DOCS

Bind, route and monetize via the BRIDLE API.
CONCEPTS

BRIDLE is a resource control layer. You register digital resources (agents, GPUs, APIs, PCs, wallets, datasets), and BRIDLE classifies, routes and meters them.

Every resource has a type, status, visibility and a set of connections describing how it composes with other resources.

REGISTER A RESOURCE

POST a resource definition to the registry. Authenticate with a workspace API key.

curl https://api.bridle.net/v1/resources \
  -H "Authorization: Bearer $BRIDLE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "type": "API",
    "name": "Internal Pricing API",
    "endpoint": "https://api.example.com/pricing/v2",
    "visibility": "TEAM",
    "tags": ["pricing", "rest"]
  }'
ROUTING

Connect resources to describe how they compose. Routing is declarative — BRIDLE handles dispatch and metering.

POST /v1/routes
{
  "from": "res_agent_alpha",
  "to": ["res_dataset_embed", "res_api_pricing"],
  "compute": "res_gpu_vision_01",
  "settle": "res_wallet_treasury"
}
MONETIZATION

Set a resource's visibility to MONETIZED and assign a rate. Earnings settle to your connected wallet on the configured cadence.

  • PRIVATE — only you
  • TEAM — workspace members
  • PUBLIC — listed, no fee
  • MONETIZED — listed, per-call fee, settled
API REFERENCE
GET/v1/resourcesList all your resources
POST/v1/resourcesRegister a new resource
GET/v1/resources/:idResource detail + health
POST/v1/routesCreate a routing flow
GET/v1/analyticsUsage, errors, earnings
POST/v1/payoutsTrigger settlement
TERMINOLOGY
Resource
A bound, addressable unit on the network.
Route
A composition of resources into a flow.
Settlement
Payout from monetized usage to a wallet.
Heartbeat
Health signal from PC/GPU workers.