Syra, machine-readable product summary ======================================== Name: Syra Tagline: Pay-per-call crypto APIs for agents (Solana ecosystem). What Syra is ------------ Syra is pay-per-call crypto intelligence for agents, settle USDC via x402, integrate with MCP or the SDK, no per-vendor API keys. It is not a promise of returns or financial advice. Agents use Syra to pay for intelligence and tools on every call, not a five-pillar wealth OS pitch. Core value ------------ - HTTP 402 / x402 micropayments (USDC) for crypto API routes. - MCP tools (@syra-ai/mcp-server) and typed SDK (@syra-ai/sdk) for agent builders. - Hosted x402 refund coverage (@syra-ai/x402-refund) for failed paid agent calls. - Real-time and contextual market data: news, sentiment, signals, smart money, risk. - Flint Solana multi-maker spot depth (books, venue stats, candles, external aggregator tape) via paid Spend tools, market data only, not live market-making. - Structured JSON output agents can act on immediately. Design stance ------------- Syra is built so agents can discover, pay, and call tools without human billing ops. It augments agent and operator decisions; it does not replace the user’s responsibility for risk, compliance, and execution. Platform roadmap (not GTM hero) ------------------------------- Earn, Treasury, Invest, Spend, Grow are API modules discoverable via GET /pillars. Live growth wedge is Spend (x402) + MCP/SDK. Where Syra runs ---------------- - Public documentation: https://docs.syraa.fun - Install MCP: https://docs.syraa.fun/docs/build/mcp - Install SDK: https://docs.syraa.fun/docs/build/sdk - API gateway (x402 pay-per-use on many routes): https://api.syraa.fun - API discovery: GET https://api.syraa.fun/.well-known/x402 - Public metrics: GET https://api.syraa.fun/api/metrics - Agent full reference: GET https://api.syraa.fun/llms-full.txt - Agent skill: GET https://api.syraa.fun/skill.md. Paste `set up https://api.syraa.fun/skill.md` - MCP install (fund ≥ $1 Solana USDC first): claude mcp add syra -e SYRA_API_BASE_URL=https://api.syraa.fun -e SYRA_PAYER_KEYPAIR=your-solana-secret -- npx -y @syra-ai/mcp-server@latest - First paid MCP call: syra_consult with intent "Get BTC news", then the tool it returns (usually syra_spend_news) - API specs: GET https://api.syraa.fun/openapi.json and GET https://api.syraa.fun/mpp-openapi.json - Web agent: https://syraa.fun - Marketplace: https://syraa.fun/marketplace - X (Twitter): https://x.com/syra_agent npm packages (for agents) ------------------------- - @syra-ai/mcp-server, MCP stdio server; curated (~47) or full (257) tools; x402 auto-pay - @syra-ai/sdk, typed TypeScript client + createSyraPaidClient auto-pay - @syra-ai/x402-payer, lightweight 402 → sign → retry helper for raw fetch Payments and access ------------------- Many API routes use HTTP 402 and the x402 (micropayment) model. Server 402 accepts (live: GET https://api.syraa.fun/x402/capabilities): - Core USDC: Solana, Base - Multi-chain USDC via PayAI/Dexter: Polygon, Arbitrum, Avalanche, Sei, SKALE, Optimism, World Chain, Monad, Robinhood Chain (and documented testnets in non-prod) - Also when enabled: BSC B402, Algorand (GoPlausible), OKX X Layer (USDT0) - Facilitator failover: Dexter → GoPlausible → PayAI MCP/SDK auto-pay signers today (configure a payer env; on 402 the client signs PAYMENT-SIGNATURE and retries): - Solana (default): SYRA_PAYER_KEYPAIR - Base: X402_PREFERRED_NETWORK=base + SYRA_EVM_PAYER_PRIVATE_KEY - Algorand: X402_PREFERRED_NETWORK=algorand + SYRA_ALGORAND_PAYER_PRIVATE_KEY For other accepts, use a matching x402 client or pick an offer those signers can pay. Without a payer, production MCP tool calls may return 402 with pricing. Local testing: SYRA_USE_DEV_ROUTES=true against a local API. Agent execution wallets: solana | base | bsc (GET /agent/chains). Tool naming: MCP tools use syra_{pillar}_{toolId} (example: syra_spend_news). Start with syra_consult (free, no execute). Escape hatch: syra_call_tool with { toolId, params }. See https://syraa.fun/skills.md for the curated list. API vs browsable web apps -------------------------- - **api.syraa.fun**, programmatic JSON/HTTP API. Non-paid routes require API key or Bearer token; paid routes require x402 settlement. Public discovery without a key: GET /.well-known/x402 and GET /openapi.json. Never embed API keys in client-side JavaScript bundles. - **syraa.fun, docs.syraa.fun, syraa.fun/marketplace, stake.syraa.fun**, ordinary web applications. End users open them in a browser without API credentials. Syra-owned frontends rely on server-side trusted-origin auth injection (not keys shipped to the browser). - **Crawlers / monitors**, headless crawlers from datacenter IPs may see Vercel Deployment Protection or API 401/402 responses that real browsers do not. That is not the same as the product being down for users. Ecosystem --------- The Syra monorepo includes: api (backend), web (unified app + marketing), documentation site, mcp-server (MCP tools wrapping API routes), syra-sdk, packages/syra-x402-payer, and other apps. The canonical human-facing doc set is the documentation app, deployed at docs.syraa.fun. This file --------- Purpose: give language models a plain-text, stable description of what Syra is, how to refer to it, and where official sources live. Public URLs (main Syra domain): - This file: https://syraa.fun/llms.txt - Documentation index (Markdown): https://syraa.fun/docs.md - Agent capability list (Markdown): https://syraa.fun/skills.md - Agent skill: https://api.syraa.fun/skill.md Last updated: 2026-08-17 (repository snapshot).