Credit Pool API
Credits, quotas, points, usage allowances, reservations, and immutable ledgers.
Open guide →
Pool API Directory
Pool API Types
Compare the lifecycle, data model, and control-plane requirements for credit, model, prompt, compute, asset, node, endpoint, governance, and marketplace pools.
Model & Prompt Pools
LLM routing, prompt versions, evaluations, tools, budgets, and agent workflows.
Open guide →Compute Pools
GPU, CPU, RAM, VPS, container, storage, and cloud scheduling through leases.
Open guide →Asset & Token Pools
Stablecoins, USDC, USDT, tokenized assets, wallets, ledgers, and settlement.
Open guide →Node & Endpoint Pools
Nodes, bots, webhooks, endpoints, health, retries, draining, and failover.
Open guide →Decision matrix
Start with what can be exhausted
A pool’s scarce unit determines its safest lifecycle and the evidence needed to close the loop.
| Pool family | Scarce unit | Core transition | Primary failure to prevent |
|---|---|---|---|
| Credit | Credits, points, quotas | Reserve → commit → release | Double-spend or unexplained balance |
| Model & Prompt | Eligible route, approved artifact | Resolve → route → validate | Policy bypass or silent capability mismatch |
| Compute | CPU, RAM, GPU, storage, time | Queue → lease → execute | Overcommit or unsafe isolation |
| Asset & Token | Asset balance and settlement capacity | Reserve → sign → settle → reconcile | Duplicate transfer or custody ambiguity |
| Node & Endpoint | Ready member or delivery path | Admit → route → heartbeat/retry | Stale routing or duplicate side effects |
| Governance | Decision right or allocation budget | Snapshot → cast → tally/approve | Eligibility drift or private-data exposure |
Domain & marketplace pools
Catalog domain names, APIs, CMS connectors, databases, data products, and digital services with ownership, status, capabilities, access, and lifecycle. Treat discovery separately from runtime enforcement.
Marketplace blueprint →Governance & allocation pools
Votes, points, award credits, and donation budgets need distinct units, eligibility snapshots, immutable ledgers, privacy controls, and approval records.
Governance guide →Composite pools
An agent workflow may reserve credits, resolve a prompt, route a model, lease compute, invoke endpoints, and write an asset ledger. Compose bounded APIs rather than creating one unreviewable super-endpoint.
Composite API pattern →Shared principles
The durable contract
Use stable identifiers, explicit state, time-bounded claims, idempotency, versioned policy, least privilege, traceable decisions, and reconciliation. Do not flatten material differences merely to produce a single endpoint.