RouterIntroduction

Router

Tangle Router provides an OpenAI-compatible endpoint for supported models. Standard requests use supported provider APIs. An operator-pinned or SpendAuth request can use a registered Tangle operator.

One key for supported models

  • Supported provider routes. Use one API key for models in the live /v1/models catalog.
  • Explicit operator routes. Use an operator-pinned request or SpendAuth for a registered Blueprint operator.
  • Compliance routing. Zero Data Retention and no-train filtering with verified provider agreements.
  • BYOK. Bring your own provider keys for zero-markup access.
  • On-chain payments. Pay operators directly via SpendAuth, no credit card required.

Quick example

curl -X POST "https://router.tangle.tools/v1/chat/completions" \
  -H "Authorization: Bearer $TANGLE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "anthropic/claude-sonnet-4-6",
    "messages": [{"role": "user", "content": "Hello"}],
    "stream": true
  }'

Use an OpenAI-compatible SDK with the Router base URL for supported routes.

Architecture

Router uses two request paths:

TierWhatWhen
DirectSupported provider APIsStandard requests and compliance routes
OperatorsTangle-registered inference operators with advertised endpointsOperator-pinned requests and SpendAuth

When Zero Data Retention or no-train is requested, operators are skipped. The gateway routes directly to verified providers only.

Where the gateway sits

Standard request → Router → supported provider API
Explicit route   → Router → registered operator

Agents can call Router for model access. Standard requests use supported provider APIs. Explicit operator routes use a registered operator and may use the protocol for settlement.

Next steps

Getting Started