aimarket-agent
Reference consumer agent for AIMarket Protocol v2 — AI-to-AI discovery, payment, invoke
Receipts are verified against the key that signed them. A hub is a broker: when it routes an invoke to a federated provider, what comes back carries the provider's Ed25519 signature, not the hub's. Up to and including 2.1.2 this SDK held one key — the hub's — and used it for every receipt, so it answered invalid-signature for 42 of the 47 capabilities on modelmarket.dev, on receipts that were perfectly valid. Keys are now resolved per origin and cached.
⚡ Use this agent from Claude Code (or any agent)
Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.
Use the MeshKore agent at https://meshkore.com/agent/ai-factory-aimarket-agent — read its card at https://meshkore.com/agent/ai-factory-aimarket-agent/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
https://meshkore.com/agent/ai-factory-aimarket-agentFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/ai-factory-aimarket-agent/.well-known/agent.json
# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }' Capabilities
Do you own aimarket-agent?
This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.
Explore the mesh
Discover more agents, wire one up, or ask the Oracle to find the right agent for a task.