treg_x_search_posts $0.001 per call

x.search.posts — routed: best of 3 providers, own keys first. Search X (Twitter) posts by keyword — provider-native rows in `posts` (Multi-provider (routed) · X (Twitter))

For AI agents: call treg_x_search_posts
POST https://toll402.dev/v1/p/treg.x.search.posts
{
 "q": "…"
}
Answers 402 with x402 payment requirements; pay with any x402 client (@x402/fetch, x402 for Python, toll402-client, toll402-mcp) or send a prepaid-credits key as x-toll402-key (https://toll402.dev/credits). Paid per call via x402 (USDC on Base) or with a prepaid-credits key (x-toll402-key, card at /credits); charged only on success. Start at /llms.txt or connect the MCP server: npx -y toll402-mcp · remote https://toll402.dev/mcp.

Input schema

{
 "type": "object",
 "properties": {
  "q": {
   "type": "string",
   "description": "identity"
  }
 },
 "additionalProperties": true,
 "description": "Send what you know; treg sends each provider only the fields it accepts ({q}). On a miss it tries the next provider, cheapest first. Options are X-Treg-Route-* headers, never body fields. The answer is {output, raw, _treg}; X-Treg-Served-By names the provider. When you sent a domain, _treg.domain_match says whether the hit's mailbox domain matches it."
}

MCP

{"mcpServers":{"toll402":{"command":"npx","args":["-y","toll402-mcp"],"env":{"TOLL402_WALLET_KEY":"0x..."}}}}

All tools · OpenAPI