Get AI-powered poker decisions via x402 micropayment from multiple LLM backends.
What it does
This x402-enabled endpoint provides AI poker decision-making advice, drawing on multiple large language model backends including ChatGPT, Claude, Grok, and Deepseek. Callers pay per request using USDC on the Base network via the x402 payment protocol, with a maximum cost of 0.05 USDC per decision (50000 units in 6-decimal USDC).
The endpoint is live and returns a standard x402 402 Payment Required challenge when called without payment. It accepts POST requests to `/api/decision`. Beyond the description in the x402 challenge, no documentation, OpenAPI schema, or usage examples are publicly available — the server returns 404 on all non-endpoint routes including `/docs`, `/api`, and `/README`. The exact request body format (e.g., how to specify hand cards, community cards, pot size, position, or which AI model to use) is unknown from the available material.
Because of the lack of documentation, callers will need to experiment or obtain out-of-band instructions to construct valid requests. The payment address is `0xb1D321629B47DA8886cb2d1F30E377F01C8d2189` and the accepted asset is USDC (`0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`) on Base.
Capabilities
Use cases
- —Getting AI-recommended actions (fold, call, raise) for a given poker hand
- —Comparing poker advice across multiple LLM providers (ChatGPT, Claude, Grok, Deepseek)
- —Integrating automated poker decision support into a poker training tool
- —Agent-driven poker play using micropayment-gated AI advice
Fit
Best for
- —Developers building poker training or simulation tools
- —AI agents that need on-demand poker strategy advice
- —Experimenting with x402 micropayment-gated LLM endpoints
Not for
- —Production use requiring well-documented, stable APIs with schemas
- —Non-poker game strategy or general-purpose LLM chat
- —Users who need free or subscription-based access rather than per-call micropayments
Quick start
curl -X POST http://x402-poker-server-production.up.railway.app/api/decision \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_token>" \
-d '{"hand": ["Ah", "Kd"], "community": ["Qh", "Jc", "10s"], "pot": 200, "model": "claude"}'Example
Request
{
"pot": 200,
"hand": [
"Ah",
"Kd"
],
"model": "claude",
"community": [
"Qh",
"Jc",
"10s"
]
}Endpoint
Quality
The endpoint is live (402 challenge confirmed) and the x402 payment metadata is clear, but there is zero public documentation, no OpenAPI schema, no examples, and no way to determine the correct request body format from available material. The request example above is entirely speculative. This is effectively a stub listing.
Warnings
- —No public documentation available — all doc routes return 404.
- —Request body schema is completely unknown; the example_request_json is speculative and may not work.
- —The outputSchema in the challenge lists method as GET, but the probe succeeded with POST — the actual expected method is unclear.
- —mimeType in the challenge is empty, giving no hint about response format.
Citations
- —Endpoint returns a live 402 x402 challenge with USDC on Base network, max amount 50000 (0.05 USDC).http://x402-poker-server-production.up.railway.app/api/decision
- —Description states: AI poker decision from ChatGPT, Claude, Grok, or Deepseek.http://x402-poker-server-production.up.railway.app/api/decision
- —Payment address is 0xb1D321629B47DA8886cb2d1F30E377F01C8d2189 and asset is USDC at 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913.http://x402-poker-server-production.up.railway.app/api/decision