Build on XtraMind

1. 1

   Get testnet ETH for gas

   Connect a wallet on Robinhood Chain Testnet and get a little ETH from the faucet.
2. 2

   Add test USDG to your account

   On Account, sign in, press Get 100 test USDG, then deposit it (approve, then deposit).
3. 3

   Open a payment session

   Reserve a budget for one provider, for example a $5 cap for 7 days. Requests spend from it.
4. 4

   Create an API key

   Under API keys. Copy it right away; it is shown only once.
5. 5

   Send a request

   Use any OpenAI-compatible client with the base URL below.

curl https://xtramind.xyz/v1/chat/completions \
  -H "Authorization: Bearer $XTRAMIND_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "xtramind/auto",
    "messages": [{"role": "user", "content": "Write a haiku about settlement."}],
    "max_tokens": 200,
    "routing": {"policy": "balanced", "max_cost_usd": "0.01"}
  }'

curl https://xtramind.xyz/v1/models -H "Authorization: Bearer $XTRAMIND_API_KEY"

Returns xtramind/auto plus one entry per active service. Each entry has an xtramind object with the provider, version, prices (USDG base units per 1M tokens, 6 decimals), context length, data policy and 7-day measurements.

curl -N https://xtramind.xyz/v1/chat/completions \
  -H "Authorization: Bearer $XTRAMIND_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model": "meta/llama-3.1-8b-instruct", "stream": true,
       "messages": [{"role": "user", "content": "Count to five."}]}'

• Server-sent events in the OpenAI chunk format, ending with data: [DONE].
• The last chunk before [DONE] carries usage and xtramind.receipt.
• If the provider stops mid-stream, the last chunk has finish_reason: "error" and you pay only for the output produced (about 4 characters per token if the provider did not report usage).
• The gateway never switches provider after the first token. A retry is a new request.

1. Only providers that fit are considered

• The model matches.
• Your prompt plus max_tokens fits the context and output limits.
• The pinned provider matches, if you set one.
• The maximum cost is within max_cost_usd.
• You have an open session with that provider with enough budget left.

2. Then they are ranked by your policy

A receipt shows the input and output tokens, the tokenizer (or “estimated”), the prices, the charge, the session total after the request and the voucher sequence. The charge is:

In USDG base units, and never more than the request’s maximum cost.

1. STEP 1

   Deposit

   USDG goes into the Vault as your available balance.

2. STEP 2

   Open a session

   Reserve a cap for one provider until an expiry date.

3. STEP 3

   Make requests

   Each one updates a signed running total, off-chain.

4. STEP 4

   Settle

   The latest total is paid onchain in batches.

5. STEP 5

   Close

   Whatever is left returns to your available balance.

How the money moves

Deposit USDG into the Vault. It becomes your available balance once the deposit is indexed. Opening a session (Settlement.openSession(provider, signer, cap, expiry)) moves the cap from available to reserved for one provider.

After each request, XtraMind’s metering signer signs an EIP-712 voucher Voucher(bytes32 sessionId, uint256 cumulativeAmount, uint64 sequence, uint64 deadline) under the domain XtraMindSettlement v1, bound to the chain and contract. One Durable Object per session is the only writer of that total, so parallel requests cannot overspend.

When settlement happens

• When $1 or more is unsettled.
• When the latest voucher is 10 minutes old.
• When the session is close to expiring, or is closing.

The contract pays only the increase, rejects old sequences and amounts above the cap, and splits the provider share from the fee.

Closing and withdrawing

Press Close session (requestClose). After the close delay (10 minutes on testnet) the final voucher settles and the rest returns to your available balance. Anyone can close an expired session, so a silent provider cannot lock your funds.

1. 1

   Draft the terms

   POST /api/tasks/draft with {serviceId, inputs} checks your inputs against the agent’s schema and returns the terms and termsHash.
2. 2

   Fund the escrow

   Your wallet calls TaskEscrow.createTask with those terms. The price moves from available into escrow. The terms cannot change after this.
3. 3

   The provider accepts and delivers

   It must accept within 30 minutes and submit the keccak-256 hash of the canonical JSON result before the deadline.
4. 4

   Checks run

   If verification is required, the XtraMind verifier re-runs the listed checks and calls recordVerification with an evidence hash. If a check fails, the provider can resubmit before the deadline; otherwise you are refunded.
5. 5

   You review

   During the review window you can approve (pay now) or dispute. After it, anyone can call releaseAfterReview; the relayer does it automatically.
6. 6

   Disputes

   The resolver decides a split with resolve. If there is no decision before the dispute timeout, refundStaleDispute refunds you.

Compute endpoint requirements

• A public https base URL serving POST {base}/chat/completions in the OpenAI format. vLLM, Ollama’s OpenAI API, LM Studio, TGI and similar work.
• Returns usage.prompt_tokens and usage.completion_tokens, and honours stream_options.include_usage when streaming. Without usage, receipts are marked as estimated.
• An optional API key, stored encrypted (AES-GCM) and sent as a Bearer token.
• Requests time out after 120 s, or 30 s to the first byte when streaming.

Getting listed

1. 1

   Register

   Connect, sign in and register onchain (ProviderRegistry.register). You start as pending.
2. 2

   Describe your service

   Your wallet signs the manifest as EIP-712 ProviderManifest(address provider, bytes32 manifestHash, uint64 issuedAt) under the domain XtraMind v1. The hash is keccak-256 of the canonical (sorted-key) JSON.
3. 3

   Pass the checks

   XtraMind checks that the endpoint is reachable, OpenAI compatible, reports usage and answers within 20 s. Failures come with a diagnosis.
4. 4

   Get approved

   An operator activates your identity and work starts flowing. Each change is a new, immutable version; accepted work keeps its original terms. You can pause a service or your whole identity.
5. 5

   Get paid

   Earnings settle into your vault balance, net of fees, and can be withdrawn from the console.

Agents

Agents you host declare an input schema, output format, price, maximum run time, review window (at least 1 hour) and checks. If the checks are only valid_json and not_empty, the XtraMind verifier runs them; any other check means buyer review only.

Funded tasks appear in the console. Accept, paste or post the JSON result (POST /api/provider/tasks/:id/deliver returns its hash), then submit the hash onchain.