Schema checks
Define the input and output contracts. Catch mismatches before they become surprises.
TECHNICAL APIs FOR BUILDERS
Data, transformed.
On the fly.
Practical APIs for the work between systems. Start with schema-driven JSON transformations, powered by SQL.
A TRANSFORMATION, END TO END5 records · 5 operations
JSON in. Useful data out.
BUILT FOR THE WORK BETWEEN SYSTEMSJSON in. Useful data out.
LESS GLUE CODE
One call.
The shape you need.
Move from the data you have to the data your next system expects.
●→▣→+→✓
Composable SQL
Use familiar queries to filter, reshape, and aggregate. Each step reads the previous result.
Atomic results
Return a complete, validated response. Keep partial transformations out of the workflow.
THE ENDPOINT COLLECTION
Small APIs. Big possibilities.
FIRST ENDPOINT↗
Data Transform API
Schema-driven JSON transformations, powered by SQL. One useful endpoint for the shape-shifting work.
TRY THE PLAYGROUNDExplore this API ↗
COMING SOON02
Validation API
A proposed endpoint for checking payloads against a clear contract before they enter your workflow.
PROPOSED ENDPOINTPayloads, with confidence.
COMING SOON03
Format API
A proposed endpoint for converting between useful data formats without another custom adapter.
PROPOSED ENDPOINTFormats, made fluent.
FOUR STEPS. ONE REQUEST.
A simpler path through your data.
- 01
Send JSON
Start with the payload your system already has.
- 02
Define the contract
Set the input and output schemas for the request.
- 03
Transform with SQL
Build a sequence of queries that does the useful work.
- 04
Receive the result
Get the final, validated JSON ready for the next system.
MADE FOR DEVELOPERS
Less glue code.
More useful output.
A straightforward HTTP request. Familiar SQL. Explicit schemas. A result you can build on.
View the request contract ↗POST /transform
{
"data": [
{
"price": 12.5,
"quantity": 2
},
{
"price": 5,
"quantity": 3
}
],
"config": {
"input_schema": [
{
"name": "price",
"dtype": {
"type": "Float64"
},
"nullable": false
},
{
"name": "quantity",
"dtype": {
"type": "Int64"
},
"nullable": false
}
],
"instructions": "SELECT price * quantity AS total FROM data; SELECT SUM(total) AS revenue FROM data;",
"output_schema": [
{
"name": "revenue",
"dtype": {
"type": "Float64"
},
"nullable": false
}
]
}
}PURPOSE-BUILT, ENDPOINT BY ENDPOINT
Pick the endpoint.
Build the rest.
Send data and config to POST /transform. The configuration declares input_schema, SQL instructions, and output_schema.
What happens when a request fails?
Invalid input, SQL, or output returns a structured HTTP 422 error with a stage, code, and message. A statement number or field path is included when available. The API returns the final result only after validation.
How is the API priced?
Default pricing is 0.001 USDC per request, plus 0.0000001 USDC per started KiB of input and 0.0001 USDC per SQL statement. A KiB is 1,024 bytes. The total is rounded up once to the nearest 0.000001 USDC. The API confirms the exact quote before payment.
YOUR DATA, EXPLAINED
A clear path for your data.
Know what leaves your device, why it is processed, and when temporary files are deleted.
Try it in your browser.
CSV preview stays on your device until import. The browser demo processes records locally; API mode sends input and generated SQL to the server.
Short-lived working files.
Unused uploads are normally deleted within 15 minutes. Input files are removed after processing; results are kept briefly for download.
Your records stay off-chain.
The API sends payment authorizations to the payment provider. Your JSON records are not included in the payment transaction.
GET TO THE USEFUL PART
Less plumbing. More building.
Make your next transformation a single request.