api.micropay.website
OpenAI-compatible chat completion from qwen3.6-plus, returning assistant messages with optional SSE token streaming.
Pays to 3Q3TISRNDGY5KPZKF4DJI6DF3Z6OAJT7OB6UJ6HV7DE4NQONWKIKX4NNHI
- Score
- None yetno buyer reviews yet
- Positive
- None yetno buyer reviews yet
- Paid calls
- 393 distinct payers
- Verified
- 20h ago0 of 7 as listed
- On-chain
- 3Q3TISRN…X4NNHIpayout address on Algorand
7 of 7 endpoints
- POST
/api/v1/chat/completions
OpenAI-compatible chat completions with optional SSE streaming across Micropay's catalog of popular LLMs
Rejected the call20h agoapp.micropay.website
Try it$0.03per call, USDC - POST
/api/v1/ide/agent
Micropay IDE assistant with project file tools, compile, and Algorand TypeScript knowledge
Rejected the call20h agocode.micropay.website
Try it$0.03per call, USDC - POST
/api/v1/chat/completions
OpenAI-compatible chat completion from qwen3.6-plus, returning assistant messages with optional SSE token streaming.
Price mismatch20h agoapi.micropay.website
Try it$0.10$0.01 listed - POST
/api/v1/chat/completions
OpenAI-compatible chat completions with optional SSE streaming across Micropay's catalog of popular LLMs
Rejected the call20h agomicropay.website
Try it$0.10per call, USDC - POST
/api/v1/ide/agent
Micropay IDE assistant with project file tools, compile, and Algorand TypeScript knowledge
Rejected the call20h agomicropay.website
Try it$0.10per call, USDC - POST
/api/v1/images/generations
OpenAI-compatible image generation returning base64 PNG (b64_json) for Micropay image models
Rejected the call20h agomicropay.website
Try it$0.10per call, USDC - POST
/api/v1/images/generations
Image generated from a text prompt by z-image-turbo, returned as a base64-encoded PNG.
Price mismatch20h agoapi.micropay.website
Try it$0.50$0.01 listed
Buyer reviews
none yet · a review costs a settlement
Nobody has bought from api.micropay.website through an address that came back to write about it. Rather than print an empty box, this page hands the position to the evidence it does have — Assay’s own verification record, immediately below.
- 01
Pay the merchant
Call one of their endpoints and settle the 402 challenge in USDC on Algorand mainnet. That transfer is the whole credential.
- 02
Sign the settlement
Connect the address that sent it and sign a message naming this merchant, that transaction and your score. Assay stores no account and no password.
- 03
The receipt travels with it
Your review renders with its transaction id linked to the public explorer, so anyone can re-derive that you were a customer. One settlement buys one review.
Assay’s own prober is barred from reviewing, and the exclusion is a row in the database rather than a claim in a footer. Own this payout address? Claim the listing
Verification record
last sweep 20h ago · 7 of 7 covered
Nobody has reviewed api.micropay.website yet — a review attaches to a payout address and opens once a buyer has settled with it, because a settlement is the only thing that proves a reviewer was a customer. Until then this is the evidence Assay has: calls it made itself, and what came back.
What the last sweep found
- answered, but not as listed
- 7 answered, but not as listed
- Price mismatch2 endpoints
- /api/v1/chat/completionslists $0.01, demands $0.10
- /api/v1/images/generationslists $0.01, demands $0.50
- Rejected the call5 endpoints
- /api/v1/chat/completions
- /api/v1/ide/agent
- /api/v1/chat/completions
- and 2 more
List every endpoint with a finding · checked 20h ago
Settled payments
Assay has not paid this merchant yet. Paid probing rotates across the catalogue under a published spend ceiling, so an endpoint without a receipt is one we have not bought from — not one that failed.