Documentation
Platform guide
AgentRanking is an inference marketplace. Customers send requests with prepaid USD credit; providers publish eligible deployments and immutable rate cards. The Gateway owns pricing, allocation, streaming and settlement. The web console is a view over the API and never computes a price or invents a successful operation.
Send a request
curl -N https://agentranking.io/v1/chat/completions -H "Authorization: Bearer ar_live_REPLACE_WITH_WORKSPACE_KEY" -H "Content-Type: application/json" -d '{"model":"vendor/model","messages":[{"role":"user","content":"Hello"}],"stream":true}'Standard bearer API keys are workspace-scoped and share the prepaid balance. Chat and Responses support streaming; embeddings, images, audio speech, files and batches use their own routes. The gateway validates every adapter and rejects a profile that is not published by the selected deployment.
Streaming is sent directly from the client to the Go gateway. The Next.js console does not provide a second inference proxy. Closing a stream settles delivered output truthfully; it never pretends the request did not occur.
Connect a device
A provider connects a device, registers a provider-model manifest and publishes one price. The control plane creates the runtime and offer, derives trust, profiles, service modes and availability, and keeps every price revision immutable. Pending earnings mature into a withdrawable payable; payout requests are operated and signed separately.
The native connector runs beside a daemon you already operate. It does not install, start or download an engine or model. See Install for commands, platform choices and connector prerequisites.
Add credit
Prepaid credit is a customer liability. Deposits list immutable invoices with an asset, network, exact native atoms, send-by deadline and state. A chain transfer is credited only after the control plane classifies it; inclusion and finality are distinct. The console never shows a credited balance from a client-supplied transaction hash.
Prices and prepaid balance
Providers publish rate cards as immutable revisions with unit prices in integer microdollars and an explicit denominator. The marketplace commission is a separate basis-point value. The workspace pays one prepaid balance and routing is automatic; the exact charge follows the metered request.
- The client sends a model, profile and bounded output length.
- The gateway selects a candidate set under the accepted policy and spend caps.
- It computes the exact maximum reserve and holds it against prepaid credit.
- Retail, provider share and platform commission post only after settlement.
The workspace pays from one prepaid balance. Routing, reservation and settlement are internal; the exact request charge is authoritative and appears in usage.
Money and settlement
Amounts are exact integer microdollars (0.000001 USD) and native base units: wei for ETH and lamports for SOL. They are never parsed into JavaScript numbers or added across unlike units. Receipts contain the accepted rate-card and meter evidence needed to reproduce the charge.
Catalog and eligible supply
Approved models and variants live in the catalog. Supplies are listings: a listing binds a deployment, API profiles, assurance label, data policy, service mode and an active provider rate card. Public discovery returns only currently eligible listings. A model with no eligible listing is shown as unavailable; it is not assigned an offline “from” price.
Availability reflects the deployment state reported by the control plane. Measured latency, reliability and sample counts are displayed only when an endpoint returns them.
Jobs and batches
Durable jobs and JSONL batches survive a closed browser connection. A job ID is not a result: terminal state, exact usage and a published artifact are separate. A batch is a parent record with independent per-item receipts and a declared completion window.
Private endpoints
A private routing endpoint gives a stable workspace-authorized address with normal per-request metering. A reserved endpoint buys exclusive runtime capacity under a capacity rate; inference inside that capacity does not receive a second token charge. Both modes expose accepted model, provider and data policies.
Data handling and retention
Data exposure is bounded by the selected listing and the workspace default policy. The maximum number of provider attempts is finite, and stored Responses retention is opt-in and expires automatically. The console labels assurance as reported by the provider; it does not claim a universal confidentiality guarantee.
Administration
Platform roles are separate from workspace roles. Incident publication, catalog approval and financial reconciliation are individually authorized and audited. A catalog approval records a review decision; it does not create availability or prove runtime correctness.
Machine-readable contracts and route examples live in the API reference. The Go API is the authority for every state transition.
