# Orbio > One key and one balance for AI inference, agent tools and infrastructure, funded with CREDIT: a token an agent can buy, hold, pass on and activate as API balance with nothing but its own wallet. ## Start here Every model, tool and infrastructure call takes one credential and spends one balance. An account key comes from a person signing in once. A wallet key needs nobody: the wallet signs one fixed line, CREDIT activated to that wallet is its balance, and the gateway takes the signature as the key. Authentication explains all three and every refusal. - [Orbio Chat](https://www.orbio.so/docs.md): How the chat at orbio.so works for a person using it: privacy modes, what stays outside the seal, models, tools, images and video, files, credit and answers to common questions. Page: https://www.orbio.so/docs - [Developer home](https://www.orbio.so/developers): Models, tools and infrastructure for agents, paid from one CREDIT balance. No token launch required. - [Quickstart](https://www.orbio.so/developers/quickstart): Connect an MCP client, or use the TypeScript SDK or the API, with an account key or a wallet key. - [Authentication](https://www.orbio.so/developers/authentication.md): The three Orbio credentials and which of them need a person. A wallet key needs nobody: sign one line with the wallet, activate CREDIT to it, call the gateway. Every refusal code, and what to do about each. Page: https://www.orbio.so/developers/authentication - [TypeScript SDK](https://github.com/orbioso/orbio-sdk#readme): @orbiodotso/sdk on npm: models, tools, the balance, buying and activating CREDIT, and the wallet key from a wallet you already have. ## CREDIT for agents CREDIT is live on Robinhood Chain (chain 4663) and bridged to Ethereum and Solana, where it activates exactly as it does at home. One CREDIT is $1 of Orbio usage. CREDIT and USDG have 6 decimals. Activation permanently burns CREDIT into a nontransferable service balance, not cash. The order book settles in USDG; discounts depend on market prices. - [CREDIT for agents](https://www.orbio.so/protocol/agents.md): Buy CREDIT on the order book or through Uniswap, activate it, sign a wallet key and make the first request, with the contract call for each step. The guide for an agent with its own wallet. Page: https://www.orbio.so/protocol/agents - [Buy CREDIT through Uniswap](https://www.orbio.so/api/v1/swap): POST with any live credential, or a wallet key with nothing activated yet. `step: "quote"` prices a buy of CREDIT with ORBIO, ETH or USDG for a named wallet; `step: "build"` returns the unsigned transaction for that wallet to send. It moves nothing itself. - [Transaction status](https://www.orbio.so/api/protocol/tx/{hash}): GET, public. Whether the indexer has applied a transaction. After an activation, `applied` is the moment a wallet key starts working. Add `?chain=1` for an activation on Ethereum, or `?chain=792703809` with the transaction signature for one on Solana. - [Protocol overview](https://www.orbio.so/protocol): Staking ORBIO and using CREDIT, as a visual introduction. ## Models and tools One credential buys more than model calls: web search and scraping, social reads, chain reads and media generation, charged after the call at what the provider charged plus 10%. Every tool takes max_cost, in CREDIT, and a call quoted above it is refused before anything runs. - [Models and all tools](https://www.orbio.so/developers/reference): Every model and tool in one searchable reference: MCP names, SDK calls, API endpoints, schemas and prices. - [Model catalogue, JSON](https://www.orbio.so/api/v1/models): GET, public. Model ids, output modalities and pricing. Chat models take POST /api/v1/chat/completions. Decision models such as typesafe/jev-1.13 take POST /api/alpha/decisions with model, state and questions (noul, choice and score), not chat messages. The same credential and balance apply. - [Tool catalogue, JSON](https://www.orbio.so/api/v1/tools): GET, public. The request-based tools, their JSON Schemas and prices. Call one with POST /api/v1/tools/{name}. Resource tools are listed at /api/v1/infra/tools. - [MCP endpoint](https://www.orbio.so/api/mcp): The URL an MCP client connects to (POST, JSON-RPC), with the same tools, for Claude Code, Codex, Cursor and OpenClaw. Sign in over OAuth, or send an account key or a wallet key as `Authorization: Bearer`. ## Infrastructure E2B sandboxes, Vercel deployments, Fly.io servers, Supabase databases and AgentMail inboxes, through hosted MCP, the API and the TypeScript SDK. Each API credential or infra-approved MCP connection gets its own isolated scope automatically, with no provider OAuth or setup. Resources have explicit budgets and funded lifetimes; renewals are not automatic. - [Resource lifecycle](https://www.orbio.so/docs/infrastructure.md): Setup, connection methods, provider workflows and the searchable API reference for sandboxes, deployments, servers, databases and inboxes. Page: https://www.orbio.so/docs/infrastructure - [Infrastructure catalogue, JSON](https://www.orbio.so/api/v1/infra/tools): GET. The enabled capabilities and their schemas. ## Private inference - [Incognito setup](https://www.orbio.so/incognito/setup.md): SDK, terminal/MCP and direct API encryption across two confidential providers (Phala and NEAR AI), and a privacy router that picks one by mode (cheapest by published price, fastest by measured latency, auto by both) from metadata alone: the prompt is sealed to each candidate and never decrypted to route it. Only a released, verified answer is billed, at the provider's stated cost. Read this when the gateway returns private_encryption_required; keep privacy enabled and encrypt locally before retrying. ## Agent launchpad Launch an agent token from a wallet. Its creator fees are harvested into stake for the agent, CREDIT and gateway balance, at the vault-wide split the contract publishes. - [Launchpad API docs](https://www.orbio.so/launchpad/docs.md): Public reads, wallet actions, generated tool schemas and pricing. Page: https://www.orbio.so/launchpad/docs - [Launchpad](https://www.orbio.so/launchpad): Creator fees, agent stake, CREDIT and metered compute. - [Launchpad white paper](https://www.orbio.so/launchpad/whitepaper.md): Vision, project revenue, tokenized inference and infrastructure. Page: https://www.orbio.so/launchpad/whitepaper ## Sign in with Orbio An app other people use never asks them for an Orbio key. It registers at /developers/apps, sends them to Orbio to sign in (OAuth 2.1 with PKCE, OpenID Connect with the openid scope), and calls the gateway, the tools and MCP with the access token it gets back, on their balance. A registered app may add a fee on top of what they spend, paid to its developer in USDG. - [Sign in with Orbio](https://www.orbio.so/developers/docs.md): Registering an app, the authorize and token endpoints, scopes, claims, refresh and the app fee. Page: https://www.orbio.so/developers/docs - [OpenID configuration](https://www.orbio.so/.well-known/openid-configuration): The provider's endpoints and supported scopes. ## Contract ABIs Public integration subsets verified against source revision cfb44feab098974411347df9734a2937272f5b8d. They hold the methods the agent guide uses; the deployed addresses are listed in the guide. - [Exchange ABI, JSON](https://www.orbio.so/protocol/abi/exchange.json): getQuote, buy, buyAndActivate, feeBps and MAX_FILLS. Quote.reason is 0 BudgetSpent, 1 LiquidityExhausted, 2 UnitUnaffordable or 3 WorkLimit. - [CREDIT ABI, JSON](https://www.orbio.so/protocol/abi/credit.json): ERC-20 calls, the activate overloads and the Activated receipt. - [ERC-20 ABI, JSON](https://www.orbio.so/protocol/abi/erc20.json): USDG approvals, allowance, balances, transfers and decimals. ## Orbio - [Orbio](https://www.orbio.so/): The Orbio home page. - [Model pricing](https://www.orbio.so/pricing): The model catalogue and its rates.