Skip to content
Sandbox
New Our Google OAuth app is CASA Tier 2 verified — ship Gmail, Calendar, and Drive without your own assessment. Learn more

Build integrations with AI.Run them on Truto.

Your agent writes the integration. Truto runs it, connects every customer’s account, and keeps it working.

Get a free sandbox Read the docs

Free for 30 days. No card. Usually ready within one business day.

Teach your coding agent Truto

/plugin marketplace add trutohq/truto-skills/plugin install truto@truto-skills

Catalog

The integration you need is probably already here.

Search 950+ integrations across 50+ categories. If yours is missing, your agent builds it.

Already in the catalog

Truto builds and maintains these. They work with Truto’s OAuth apps from day one. Bring your own OAuth app when you want your brand on the consent screen.

Not here yet

Point your agent at the vendor’s API docs. It builds the integration, and Truto runs it on the same runtime. A fix goes live on apply, with no deploy. How building works →

The runtime

AI writes the happy path. Production is the edge cases.

Your agent codes what the vendor docs say. Here is what the docs leave out. The Truto runtime already handles it.

The vendor sends
200 OK X-RateLimit-Remaining: 0
Truto handles it with
is_rate_limitedA 200 that means “slow down”
Your app gets
429 Retry-After: 30
The vendor sends
Link: <…?page=2>; rel="next"
Truto handles it with
link_headerOne of six pagination styles
Your app gets
next_cursor
The vendor sends
401 token expired × 2 requests at once
Truto handles it with
one refresh per accountUnder a lock, so a rotating token is not used twice
Your app gets
200 OK · refreshed once
The vendor sends
200 OK {"ok": false, "error": "invalid_auth"}
Truto handles it with
error_expressionAn error hidden in a 200
Your app gets
a real HTTP error
The vendor sends
POST /webhook X-Signature: sha256=9f2c…
Truto handles it with
HMAC, per vendorEach vendor signs differently
Your app gets
event · verified
Five of ten. Each one is a line of configuration, not a fix in your code.
Show the other five
Retry-After
The header can be an HTTP date or a number of seconds.
Truto reads both, or a vendor’s own header through an expression, and gives you the wait in seconds.
Query arrays
One API wants ids=1,2. The next wants ids[]=1 or ids=1&ids=2.
Four array formats (comma, brackets, indices and repeat), set for each integration or method.
Request bodies
Not every API takes JSON.
JSON, form-encoded, multipart, XML and raw bodies. XML responses come back as JSON.
Redirects
A download can redirect to another host, such as a file store.
Truto can follow the redirect without sending your customer’s credentials to the new host.
Auth
OAuth 2.0 is only one of many schemes.
Seven auth types, from API keys and OAuth 2.0 to OAuth 1.0a, JWT bearer and AWS STS.

Build or run

AI made building cheap. It made owning expensive.

Your agent writes the code either way. The question is who runs it. Truto is the runtime from your first API call, for one integration or a hundred.

Your AI agent writes this

integration.jsonmappings.jsonataSettings.tsx
  1. "auth": { "type": "oauth2" }// integration logic
  2. name: first_name & " " & last_name// field mappings
  3. <ConnectButton integration="salesforce" />// your product
AI writes everything above this line. Truto runs everything below it.

Truto runs this

All systems running

InfrastructureNo servers to deploy, scale or patchrunning
OAuth appsApproved by vendors, such as Google CASA Tier 2approved
Customer loginsEncrypted, and refreshed for every customerrefreshed 3s ago
2 a.m. failuresHandled without paging your teamhandled
Security reviewsSOC 2 Type II and ISO 27001reports ready

85integrations shipped in one sprint

50 integrations, in-housea year
On Trutoa couple of weeks

“We could maybe build 50 integrations a year… or we can do it in a couple of weeks with Truto.”

Annie GregoryPrincipal Product Manager
Read the Thoropass case study →
Read the full build-or-run comparison

Primitives

One runtime for an integration’s whole life.

Every step, from your agent’s first build to every customer. Pick a step to see what it does and the call your code makes.

1Build it

2Connect customers

3Use it in your product

1 of 8 · in Truto: Build

Generate the integration

Your agent reads the vendor’s API docs and writes the integration as one JSON file.

No integration code in your repo to maintain.

Build in the docs →
$ truto integrations build vendor-openapi.yaml my-vendor✓ wrote my-vendor.integration.json

See all primitives →

Agent skills

Install once. Then ask your agent for the integration.

The Truto skills teach Claude Code, Cursor and other coding agents the Truto API, the CLI and how to build an integration. Your agent does the work. Truto runs the result.

1Install the skills once

/plugin marketplace add trutohq/truto-skills/plugin install truto@truto-skills

Adds the skills as a Claude Code plugin.

2Ask for the integration in plain words

Say what you need, as you would to a teammate. Your agent does the rest.

your coding agent
>

Add Expensify to our app. Map its expense reports to our accounting model, and put a Connect button in Settings.

✓

Built the Expensify integration from its API docstruto integrations build expensify-docs.md

✓

Checked it: 0 problemstruto integrations lint

✓

Put it live on Trutotruto integrations apply

✓

Mapped expense reports to your accounting modeltruto unified-mappings apply

✓

Added a Connect button to Settingssrc/settings/integrations.tsx

✓

Done. Your customers can connect Expensify from Settings.

What your agent learns

  • truto-integrations-build

    Builds a new integration from the vendor’s API docs, then lints and applies it.

  • truto-unified-mappings

    Maps an integration to a unified model, such as CRM or HRIS.

  • truto-link-sdk

    Adds the connect flow to your frontend.

  • truto-jsonata

    Writes JSONata for mappings, sync jobs and workflows.

  • truto

    Knows Truto’s concepts and writes the app code that calls them.

  • truto-cli

    Runs the Truto CLI: integrations, accounts and test calls.

  • truto-operator

    Debugs a live workspace: proxy calls, mappings, sync jobs and webhooks.

  • truto-api-conventions

    Keeps base URL, auth, pagination and idempotency correct.

17integrations, up from 2

Without Truto4 months
With Trutoa few hours

“We went from 2 integrations to 17 integrations in a few hours. Without Truto, that would have taken us at least 4 months.”

PrabodhVP of Engineering
Read the Sprinto case study →

How building works →    Skills on GitHub →

Pricing

Start in a free sandbox.

Unlimited connections, API calls and companies on every plan.

Sandbox$0

Free for 30 days. No credit card.

Expansion$999

Starting price, per connector, per year.

Enterprise$1,999

Starting price, per connector, per year.

See pricing →

Support and enterprise

Want engineers on your side?

Shared Slack channels. Dedicated engineers. A new integration by Thursday if you need it.

Not a vendor. A partner.

Nothing stored by default

Every call is real-time pass-through. Truto does not store your customer’s data unless you turn on a feature that does.

Secure and compliant

SOC 2 Type II, ISO 27001, GDPR and HIPAA. Credentials are encrypted at rest with AES-256.

SOC 2 Type IISOC 2 ISO 27001ISO 27001 GDPRGDPR HIPAAHIPAA

A dedicated deployment

Truto Cloud, or a dedicated deployment that Truto runs for you.

Unified APIs you can change

Start with the pre-built unified models, then change every mapping in JSONata, per environment or per customer.

Customers

Teams that ship their integrations on Truto.

The sort of teams that read the API docs before the sales deck, and break the sandbox before the contract is signed.

SprintoUses alongside MergeThoropassMigrated from MergeSpendfloMigrated from MergeMeshaMigrated from CodatDocsBotMigrated from CarbonSiteGPTSpark2
SpringworksMigrated from Apideck
BalkanIDUses alongside MergeEvergrowthMigrated from Ampersand
Senja
Claira
Omnitrain
ZenAdmin
Cloudficient
15FiveWorkweek
Smart Tribune
Equs
You?

“After carefully evaluating multiple unified APIs, we’re confident that partnering with Truto was the optimal choice. The caliber of Truto’s product and the quality of their support have validated our decision.”

Ajay VardhanCTO
Read the Spendflo case study →

“Truto didn’t just give us an integration layer, they became a partner. They’ve been hands-on in Slack, shipped features fast, and helped us solve the real-world sync edge cases that show up only in production.”

Aaron EdwardsCEO
Read the DocsBot case study →

View all customers →

FAQs

Common questions, straight answers.

Will my customers see Truto’s brand?

Your customers see your brand name and logo in the connect screen, after a short screen that says it uses Truto. Enterprise plans can remove Truto’s branding. The vendor’s consent screen says Truto until you bring your own OAuth app, which you can do per vendor whenever you want. Merge, Nango and Apideck also start you on their own OAuth apps.

How fast can I start?

Request a free 30-day sandbox at truto.one/sandbox. No credit card is needed. Your workspace is usually ready within one business day.

Where does Truto run?

On Truto Cloud by default. If you need a single-tenant setup or a specific data processing region, Truto runs a dedicated deployment for you.

Do you cache or store my customer’s data?

Not by default. Truto fetches data from the vendor in real time on every call and does not cache or store it unless you turn on a feature that stores data, such as SuperQuery.

Try Truto

Start building in a sandbox today

Pick your integrations, submit a work email, and get a 30-day workspace — usually ready within one business day. No credit card required.

Get a free sandbox