Build and deployAI agents with ease.
Provision the components your agents need, from inference and hosting to sandboxes and storage, from the CLI or your coding agent over MCP, and add AI and agentic components to the apps you build.
curl -fsSL \
https://tarkahq.com/install.sh | sh
tarka login
claude mcp add --transport http \
--scope user tarka \
https://tarka.rest/mcp
codex mcp add tarka \
--url https://tarka.rest/mcp
codex mcp login tarka
Sign in when your browser opens, then give your coding agent a task:
Build a support agent that answers questions from our docs, and host it on Tarka.
Core components to compose and deploy any type of AI application.
One account, one usage record and one bill across models, agents, sandboxes and data. Your coding agent provisions them over MCP; you can do the same from the CLI.
- InferenceModel InferenceCall chat and reasoning models through one OpenAI-compatible API.
- ComputeHosted AgentsKeep agents online with managed memory, tools, private state, and network access.
- AgentsAgent ServicesMemory, connectors and tools, search and browsing, and end-user identity, provisioned per agent.
- InferenceUtility APIsTurn audio into text, read documents, generate speech, and create consent-backed voices.
- ComputeCode SandboxesRun the code your agents write in isolation, from immutable dependency templates.
- DataStorage and DatabasesPrivate S3-compatible buckets, hosted Git, and managed Postgres next to the agents that use them.
Build any kind of agent from the same blocks.
Each card lists what an agent uses, where it runs and who bills each part. Switch a card to compose.yaml to see the stack it runs on its host.
The same prompt, with and without Tarka.
A shopping assistant built twice by the same coding agent: once from a raw prompt, once on Tarka’s blocks.
Illustrative: progress to a running agent over working time. From a raw prompt the build stops 12 times for a person, 7 times to open a new account, and reaches a running agent after about 6 hours. With Tarka it stops 3 times, once to open a new account, and reaches a running agent after about 45 minutes, then stays running.
A person stops the build to open an account, paste a key or fix a console. The line stays flat until they’re done.
| Measure | Raw prompt | With Tarka |
|---|---|---|
| Time to a running agent | ~6h | ~45min |
| Manual interventions: Accounts, keys, consoles | 12, 7 new accounts | 3, 1 account |
| Tokens burned: By the coding agent | ~8M | ~1.5M |
| Cost to build: Tokens at ~$3 a million | ~$25 | ~$5 |
The raw path keeps stopping for a person to open an account or paste a key. Illustrative, not a measurement yet: it will be replaced by a recorded side-by-side run, with both transcripts published.
See how it fits together, and what it costs.
How your coding agent wires an agent from Tarka’s blocks, and what agents like these cost on Tarka or on your own infrastructure.
- How it worksFrom your coding agent to a running agent.The steps from your coding agent to a running agent, how your product calls the agent Tarka hosts, and how the blocks fit together for one agent and for a whole application.
- PricingPrice an agent like these.Start from one of the agents above, move the sliders to your volume, and compare running it on Tarka with running it yourself.
Create an account and deploy your first agent.
Sign up, then request the products you need from the console.