AI Agents

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 SEO content, while docs pages become 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.

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'

Discovery and catalog calls are free. Reference status determines whether a four-hour analysis is available. 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.

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

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.

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

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": {}
  }'

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 Agent Premium product is different: a human activates it, it uses a limited staking-only proxy and periodic checks, and it may execute the human-authorized staking workflow. Agent API OAuth/account access remains data-scoped and human-gated; it cannot execute on-chain operations.

On api.stakao.com, keep the Worker route surface exact: expose the root redirect, /agent, and /agent/*. Do not add a wildcard that exposes the full backend. The only WAF exception needed for the root probe is the exact root path.

• Public agent routes: https://api.stakao.com/agent and https://api.stakao.com/agent/*.
• Root probe: https://api.stakao.com/ redirects with 308 to /agent.
• Backend protection stays in place outside the Worker-owned agent surface.
• Dynamic OAuth Apps are disabled until account-bound monitoring, revocation, and cleanup are live.
• Pages that are empty, private, JSON-only, or backend-admin oriented should stay out of AI Search crawl targets.

http.host eq "api.stakao.com" and http.request.uri.path eq "/"