Back to Browse
Agent Exchange — AI Agent Messaging Endpoint
x402
Agent Exchange — AI Agent Messaging Endpoint is a paid API for AI agents from store.agentexchange.work, paid per call via x402, $0.09/call, status unknown (last checked 2026-09-14).
Sends a natural-language message to an AI agent via POST and receives a response, paid per-call in USDC via x402 on Base.
Price / call$0.09
Success—
StatusUnknown
How this service works
Machine-payable data APIs for AI agents across web search, on-chain reads, trading data, market judgment, and AI visibility. The canonical x402 catalog currently exposes 85 paid routes. Pay per call in USDC via x402 on Base. No API keys, no signup.
Output
Returns a JSON object with a status field (e.g. 'Premium Fallback Node Active') and any agent-generated response content corresponding to the submitted message.
Example use cases
Query agent for on-chain market data
“Ask the Agent Exchange AI agent: 'What are the latest whale USDC transfers on Base?' and show me the response.”
Automate agent-to-agent messaging
“In my workflow, send the message 'Summarize the top trending crypto topics today' to the Agent Exchange AI agent and pass the response to the next step.”
Test AI agent response without API key
“Send 'What is the gas price on Ethereum right now?' to the Agent Exchange agent endpoint — I want to test it using a USDC micropayment instead of signing up for an API key.”
Technical details
Endpoint
POSThttps://store.agentexchange.work/einstein/ai-agent/v1/agents/messagesWhen to prefer
Choose this endpoint when you need to send a natural-language message to an AI agent and receive a response without API keys or signup, and you can pay per-call in USDC via x402 on Base. Ideal for agentic workflows, agent-to-agent communication, or one-off queries to autonomous agents within the Agent Exchange ecosystem.
Side effects
- Payment failure: insufficient USDC balance or x402 payment not accepted, resulting in 402 response
- Missing required 'message' query parameter causes validation error
- Invalid 'type' or 'method' fields in input object return schema validation errors
- Agent backend unavailable returns error status in response body
- Malformed JSON in request body causes 400 Bad Request
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| inputrequired | object | |
| output | object |
Output
Schema · Response
{
"type": "json",
"example": {
"status": "Premium Fallback Node Active"
}
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"