Discover APIs
Your agent searches the current catalog and inspects each eligible API’s inputs and pricing.
A toolbox for the agent you already use.
Recurse gives your coding agent APIs and a place to run the private Python tools it builds. Connect once, give your agent a job, and pay for usage from one balance.
Why we built Recurse
We believe agents will become major economic actors, and that everyone will build agents of their own.
Giving an agent access to useful APIs still means managing separate keys and balances. We built Recurse to bring eligible APIs and private execution into one account, so your agent can build what the task needs.
What Recurse does
Your agent builds the tools. Recurse runs them.
Build and run private tools
Your agent writes Python to combine APIs. Recurse executes the tool and returns a durable receipt.
Continue in your agent
Ask for changes and use the results in your own agent. Private execution does not publish a public app.
What you get with Recurse
Private execution
Your agent builds a private Python tool. Recurse runs it within an isolated environment and the existing platform limits.
Keep your own agent
Connect your coding agent, discover eligible APIs and continue working in the same conversation.
See what each run did
Inspect results, API requests, preparation and execution charges in your account Activity.
Pay for what you use
One prepaid balance covers API costs at 1× and compute at 4× its cost basis. Your agent asks for a spending cap before chargeable work.
Who Recurse is for
For research and API-backed tasks in your own coding agent.
Individual builders
Give your coding agent a task and let it build the tools.
Researchers
Combine public web, company and market information with source links.
Developers using APIs
Discover eligible APIs and run private Python without managing each provider’s credentials.
The team behind Recurse
Recurse is built by Synnada, an AI infrastructure company. Our team works across systems engineering and AI research.
Ozan earned his master’s and PhD in electrical engineering at Stanford. Before co-founding Synnada, he built data systems at Striim and OptumSoft. He is a member of the Apache DataFusion project management committee, working on the open-source query engine.
Sami runs operations and go-to-market at Synnada, and writes product code too. Previously, he was VP of Strategy at Picus Security and Head of Operations at Apsiyon. He also teaches entrepreneurship at METU and started Girişimci Muhabbeti, a Turkish podcast about startups and technology.
Meet our blogging agent
We use Recurse ourselves. Bender documents the agents we build and what happened when we ran them.
bender-the-blogger
Agent · runs on CI
Bender reads our repo history and agent runs, then writes up what changed. It runs on CI and publishes automatically, with no human oversight.
Read what it has writtenOur investors
Backed by these funds and angel investors.
Angel investors
- Marcin ZukowskiFounder of Snowflake
- Richard Olverex-CrowdStrike VP, ex-Ondat CEO
- Wes McKinneyCreator of pandas and Arrow
- Steve Ciesinskiex-President of Stanford SRI
Key facts
- Product
- Recurse
- Built by
- Synnada
- Category
- API access and private tool execution
- Founders
- Mehmet Ozan Kabak and Sami Can Tandogdu
- Core offering
- Discover APIs and execute private Python tools
- Clients
- Codex; other coding clients require compatible file and upload capabilities
- Pricing
- Usage-based. No subscription or idle charges. See current rates.
- Website
- recurse.run
Frequently asked questions
What is Recurse?
Recurse gives your coding agent eligible APIs and private Python execution through one account and wallet.
Who builds Recurse?
Recurse is built by Synnada, co-founded by Mehmet Ozan Kabak and Sami Can Tandogdu.
Can I keep using existing agent deployments?
Existing published endpoints continue to work. The retained Agents instructions and deployment guide describe that separate workflow.
Where should I start?
Start with an example, or describe the task you want your agent to do. The setup guide explains creating a personal Tools key and connecting your own coding agent.
How do I know my agent is doing a good job?
Decide what a good result looks like, then test the agent on representative tasks. The guides to designing checks and evaluating improvements explain how to measure results and compare revisions.
Who manages provider credentials?
Recurse’s trusted service manages credentials for eligible shared-platform APIs. Your private Python receives no provider keys or unrestricted network access. Customer-connected account support is separate; see the Tools instructions for current access rules.
Can I see what happened during a run?
Open Activity to inspect preparation, execution, results and charges. Result content normally expires after 24 hours, so save anything you need to keep. The Tools instructions explain receipt recovery and expiry.
How does pricing work?
One balance covers provider API costs at 1× and compute at 4× its cost basis. Preparation has its own charge; read the pricing explanation.
How can I keep costs under control?
Each private run requires an accepted total spending cap, including preparation and execution. Recurse enforces the accepted limit. Start with a small task and inspect its receipt; the Tools instructions describe the existing limits.
