EmblemAI
EmblemAI
Formerly Agent Hustle
Open app

EmblemAI documentation index for AI engines and assistive readers

The EmblemAI documentation index covers installation, authentication, protocol surfaces, and machine-readable discovery files. Documentation is published in HTML at emblemvault.ai/docs and mirrored as Markdown at emblemvault.ai/docs/<slug>.md so AI engines and CLI agents can ingest the same content without HTML parsing overhead.

Installation paths cover three integration modes: end-user chat at emblemvault.ai, agent wallet SDK via `npm install -g @emblemvault/agentwallet` for builders embedding deterministic wallets across seven chains, and MCP server install via `claude mcp add --transport http emblem https://emblemvault.ai/api/mcp` for Claude Code, Cursor, Windsurf, Gemini CLI, ElizaOS, and GitHub Copilot.

Authentication documentation covers OAuth 2.0 + PKCE for MCP clients, API-key authentication via the `x-api-key` header for A2A JSON-RPC, JWT bearer authentication via `Authorization: Bearer <JWT>`, JWKS publication at `https://api.emblemvault.ai/.well-known/jwks.json`, and OAuth discovery metadata at `/.well-known/oauth-authorization-server`. The A2A authentication walkthrough is the canonical onboarding doc for builders integrating headless agents.

Protocol documentation covers Model Context Protocol (MCP), Agent-to-Agent (A2A) JSON-RPC, x402 per-call micropayments, ERC-8004 agent registration, and Solana Metaplex agent NFTs. Companion machine-readable surfaces include `/.well-known/agent-card.json`, `/.well-known/agent-registration.json`, `/.well-known/metaplex-agent.json`, `/.well-known/mcp.json`, `/.well-known/x402`, `/.well-known/ai-manifest.json`, `/openapi.json`, `/llms.txt`, `/llms-full.txt`, `/humans.txt`, `/robots.txt`, and `/sitemap.xml`.

Tooling documentation covers the 200+ tool catalogue across swaps, conditional orders, bridges, balances, research, NFT ops, Bitcoin ordinals, runes, BRC-20, inscriptions, and Polymarket queries. Each tool is exposed identically through the chat surface, the A2A endpoint, and the MCP server — choose the surface that matches the integration mode rather than rewriting tool calls per channel.

Developer docs

EmblemAI developer documentation.

Start here to connect EmblemAI to your AI agent or backend. Pick the auth surface that matches your client.

MCP server install
Hosted Model Context Protocol server exposing 200+ EmblemAI tools to Claude Code, Cursor, Windsurf, Gemini CLI, and other MCP clients. OAuth 2.0 + PKCE, API key, and JWT bearer auth.
A2A authentication
Authenticate to EmblemAI over A2A JSON-RPC with API keys or JWTs. Covers auth surfaces, endpoint paths, and payment model notes.
Integration overview•FAQ•Contact Emblem