NewConnections · MCP and OpenAPI as one tool contract

Recursive inference to train your own models and agents

One endpoint for every model in the catalog. Every task your agents finish becomes training signal for a model you own.

For developers

One API.Every model.

Point the OpenAI SDK at Allocate and call any model in the catalog by name. Switch models without a deploy, and fine-tune the open weight ones into a model you own.

chat completions
curl https://api.allocate.network/v1/chat/completions \
  -H "Authorization: Bearer $ALLOCATE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "moonshotai/kimi-k3",
    "messages": [{ "role": "user", "content": "Summarise this ticket." }]
  }'
Models in the catalog
Regions for compute and data
OpenAICompatible endpoint, same SDKs

Your data.Your weights.

Captured as you work

Every turn your agents take is written to RecursiveDB with the outcome that followed it: merged, reverted, approved, refunded.

Recursive training

Compaction turns those records into training pairs. A run fine-tunes the open weight base you picked, on the work your own team did.

Adapters served per tenant

The adapter is served on your tenant under your own model name. Export the weights whenever you want to take them elsewhere.

Every agent gets a computer.

One container per tenant

Agents run on machines inside your own cell. Nothing shares a runtime with another customer.

Pinned to a region

Compute and data stay where you put them: the United States, Europe or South Africa.

Harness swapped by pin

The harness is a pinned build. Move your tenant forward or hold it back without touching your code.

runnerza-1liveharness760d3f79guest8 cpu · 8 GBregionsus-1 · eu-1 · za-1

Every tool, one contract.

MCP servers and OpenAPI specs are both inputs. Allocate turns them into a single tool contract, so an agent sees the same shape whatever it is calling and you connect a new service without shipping code.

Code mode goes further: the agent writes one short program and calls many tools in a single round, instead of burning a turn on every call.

agent.ts
connections: [
  {
    name: "jira",
    mcp: "https://mcp.atlassian.com/v2/mcp",
    env: "ATLASSIAN_API_KEY",
    tools: ["searchJiraIssuesUsingJql"],
  },
]
Build on your own

Sign up, mint a key, and send your first request in a minute.

  • One key for every model in the catalog
  • A computer for every agent you run
  • Experiences captured while you work
  • Metered per second, no seat licence
Enterprise

Your own cell, in your own region, with the paperwork your risk team asks for.

  • A single tenant cell in your region
  • Weights and data you can export
  • Security review and a signed DPA
  • A direct line, not a ticket queue