> For the complete documentation index, see [llms.txt](https://docs.zerve.ai/zerve-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zerve.ai/zerve-docs/notebooks/language-interoperability.md).

# Language interoperability

Pass data between Python, R and SQL blocks in the same project.

You can mix Python, R and SQL blocks in one project, and pass data between them. A dataframe created in a Python block can be used in an R block connected after it, and the other way round. A SQL block can query a dataframe from a Python block.

## How it works

When a block runs, its outputs are saved in common formats, such as **Parquet** for dataframes, along with information about each variable. Each language has its own runtime, which reads those saved results. So you don't need to write code to convert data between languages.

## Example

A SQL block pulls trades from your warehouse. A Python block cleans them and calculates returns. An R block fits a statistical model to the returns, using an R package your team prefers.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zerve.ai/zerve-docs/notebooks/language-interoperability.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.