AI Agents

How AI agents find Stakao, pay 3 USDC with x402 on Base for an allocation analysis, use OAuth account reads and stay clear of staking execution.

Updated 2026-10-13

Then €19/month$20/month. Card required. Cancel before your trial ends to avoid charges.

01

Discovery surface

Agents should start from public, stable documents before attempting paid allocation calls.

The human site owns durable context: /docs, the Markdown version of every docs page, /llms.txt, /llms-full.txt, /strategies.md, /openapi.json, product metadata, and blog explainers. The API subdomain owns the narrow agent runtime surface at https://api.stakao.com/agent.

The split is intentional. Blog pages remain editorial content, while docs pages are the canonical reference input that agents can copy, fetch, cite, and convert into tool calls.

  • Use /docs/ai-agents as the canonical human and crawler reference.
  • Use /docs/ai-agents.md when an agent wants raw Markdown without layout.
  • Use /llms.txt for site-wide context, priorities, safety boundaries, and links.
  • Use /llms-full.txt when the full canonical corpus is needed in one context window.
  • Use https://api.stakao.com/agent for live API discovery, OpenAPI, MCP, price metadata, and x402 instructions.

Fetch the public AI surfaces

bash

curl -sS https://stakao.com/llms.txt
curl -sS https://stakao.com/docs/ai-agents.md
curl -sS https://api.stakao.com/agent \
  -H 'Accept: application/json'
curl -sS https://api.stakao.com/agent/openapi.json \
  -H 'Accept: application/openapi+json'
02

Start here

The complete agent flow is discover → catalog → reference status → preflight → HTTP 402 → payment → retry → structured result.

Discovery and catalog calls are free. Reference status reports the freshness of the latest reference analysis, so an agent can tell whether a payable snapshot is current. Preflight validates wallet-specific requests before payment. A fresh payable request returns HTTP 402; the agent reads the x402 headers, pays in USDC on Base, retries the exact request, and receives a structured informational result.

Fetch the full machine-readable entrypoints

bash

curl -sS https://api.stakao.com/agent/llms.txt
curl -sS https://stakao.com/llms-full.txt
curl -sS https://api.stakao.com/agent/errors.json
03

Agent API and x402 payments

The public API is intentionally small: it sells informational allocation analysis, not account access or staking execution.

Agents can request a direct model portfolio snapshot or a wallet-specific allocation analysis. The current public agent price is 3 USDC through x402 on Base.

For wallet-specific analysis, call free preflight first. The preflight response returns the Stakao-generated client_request_id that must be reused in the paid request body. Reusing that id with a different body returns a conflict instead of creating a second paid action.

  • Direct model portfolio: GET /agent/allocation-analysis/model-portfolio.
  • Wallet-specific flow: POST /agent/allocation-analysis/allocation/preflight, then POST /agent/allocation-analysis/allocation.
  • Payment protocol: x402 v2.
  • Payment rail: USDC on Base.
  • Result: compact JSON with decision, product, and payment fields.

Probe the direct paid model portfolio endpoint

bash

curl -i 'https://api.stakao.com/agent/allocation-analysis/model-portfolio?catalog_item_id=quant_strat' \
  -H 'Accept: application/json'

Start the wallet-specific preflight

bash

curl -sS -X POST 'https://api.stakao.com/agent/allocation-analysis/allocation/preflight' \
  -H 'Content-Type: application/json' \
  -d '{
    "wallet_address": "5YourBittensorWalletAddress",
    "catalog_item_id": "ai_agent",
    "config": {}
  }'
04

Safety, OAuth, and crawl boundaries

Stakao keeps public agent commerce separate from private account operations and on-chain staking execution.

The Agent API is informational only. A paid result can include the status ANALYZED, which means an analysis was stored. It does not mean that Stakao executed staking, created a delegate transaction, opened an account session, or gave investment advice.

The AI Agent strategy is a different product. A person activates it in the Stakao app, it runs through a limited staking-only permission, and a rules-based risk engine decides every trade. Agent API OAuth and account access remains data-scoped and human-gated; it cannot execute on-chain operations.

Only the routes declared in the contract are public. Any other path returns the canonical not_found error, so integrations should not guess routes.

  • Public agent routes: https://api.stakao.com/agent and https://api.stakao.com/agent/*.
  • Dynamic OAuth Apps are disabled until account-bound monitoring, revocation, and cleanup are live.
  • Private account and dashboard pages are not crawl targets.