canonical: https://jentic.com/apis/blocklottos.com/blocklottos # Block Lottos API The Block Lottos API reports on-chain lottery draws and runs a self-serve advertising placement flow for the platform. It reads the current jackpot, draw history, and cryptographic draw proof, lists a wallet's tickets, and checks a wallet for winning prizes. It also lists available ad sizes, submits and activates ad placements, builds the on-chain transaction for a lottery ticket, and tracks an ad submission's status by id. The surface is split between read-only lottery and jackpot data and the advertising submission workflow, with on-chain actions authorised by the wallet transaction the caller signs rather than by an account credential. ## For AI agents Read on-chain lottery draws and jackpots, check a wallet's tickets and prizes, and submit, activate, and track advertising placements on the Block Lottos platform. ## Scope Does not handle payment settlement, wallet custody, or identity verification. Use for on-chain lottery data and ad placement submission only. ## Capabilities - Read the current jackpot, lottery statistics, and full draw history - Verify a draw with its published cryptographic draw proof - List the tickets held by a wallet and check it for winning prizes - Build the on-chain transaction a wallet signs to buy a lottery ticket - List available ad sizes and submit an advertising placement - Activate a submitted ad and track its status by submission id ## Use cases ### AI agent lottery status assistant An AI assistant needs to answer lottery questions and check a user's wallet for winnings without the user opening the site. Through Jentic the agent reads the current jackpot, pulls the draw history, and checks a wallet for prizes, then reports back. Because the read operations need no credential, the agent can answer these questions immediately and only builds a signed transaction when the user actually wants to buy a ticket. Example prompt: Search Jentic for 'check a wallet for lottery prizes', call GET `/api/lottery/jackpot` for the current pot, then GET `/api/lottery/check-prizes/{wallet}` for the user's wallet. ### Ad placement submission An advertiser workflow needs to submit and activate a placement on the platform programmatically. The ad-sizes, submit, and activate operations list the formats, register a placement, and turn it live, while the status lookup reports where a submission stands. This lets an agent run an ad buy end to end and confirm it is active. Example prompt: Call GET `/api/ads/sizes` to pick a format, POST `/api/ads/submit` to register the placement, then GET `/api/ads/status/{submission_id}` to confirm it moves to active. ### Draw verification and auditing A trust-and-transparency workflow needs to verify that lottery draws were fair. The draw-history and draw-proof operations return past draws and their cryptographic proof, so an agent can present verifiable draw results rather than an unaudited number. This is useful for surfacing provably fair outcomes to end users. Example prompt: Call GET `/api/lottery/draw-history` for recent draws, then GET `/api/lottery/draw-proof` to fetch the proof a user can independently verify. ### Ticket-purchase transaction building A wallet-connected app needs to let a user buy a lottery ticket without custodying funds. The build-ticket-transaction operation returns the on-chain transaction for the user's wallet to sign, keeping key custody with the user. Pairing it with the tickets lookup lets the app confirm the purchase landed after the user signs. Example prompt: Call POST `/api/lottery/build-ticket-tx` to get the unsigned transaction for the wallet, then GET `/api/lottery/tickets/{wallet}` after signing to confirm the ticket. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/api/lottery/jackpot` | Get the current jackpot | | GET | `/api/lottery/draw-history` | List past lottery draws | | GET | `/api/lottery/draw-proof` | Fetch the cryptographic draw proof | | GET | `/api/lottery/check-prizes/{wallet}` | Check a wallet for prizes | | POST | `/api/lottery/build-ticket-tx` | Build a ticket-purchase transaction | | GET | `/api/ads/sizes` | List available ad sizes | | POST | `/api/ads/submit` | Submit an advertising placement | | GET | `/api/ads/status/{submission_id}` | Check an ad submission status | ## Why Jentic - **Setup:** Wiring the Block Lottos API by hand means calling its open lottery and ad endpoints and constructing on-chain transactions for the user's wallet yourself. Through Jentic you install once, import it from the API Directory, and your agent calls it, with no key to configure. - **Permission scoping:** The Block Lottos API exposes lottery-read and ad operations, so a rule bounds which of them the agent may call: reading jackpots, draw history, and prize checks, without the ad-submission or ticket-transaction operations unless you add them. You choose the allowed set, so the agent only runs the operations you pick. - **Credential handling:** Block Lottos needs no API credential, so there is nothing to store; on-chain actions are authorised by the wallet transaction the user builds and signs, never by a key sitting in the agent's context. - **Discovery method:** Agents search Jentic by intent such as 'check a wallet for lottery prizes' or 'submit an ad placement', and Jentic returns the matching Block Lottos operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Native Ads** — Native Ads runs a publisher ad network as an alternative channel for placing advertisements - **Facebook Graph API** — The Facebook Graph API places and manages ad campaigns across Meta's platforms - **LinkedIn** — LinkedIn runs professional-audience ad campaigns as an alternative advertising channel ## FAQ ### Is there a Block Lottos API MCP server? You don't need an MCP server to give your agent the Block Lottos API. Jentic connects it directly from the API Directory: import it and your agent calls the lottery-read and ad operations on demand without loading another server's tool definitions into its context. ### What authentication does the Block Lottos API use? The Block Lottos API defines no authentication scheme in its OpenAPI spec: the lottery and ad read endpoints are open, and on-chain actions are authorised by the wallet transaction the caller signs rather than by an API key. When you call it through Jentic, there is no key to manage and you still control which operations your agent may call. ### Can I check a wallet for lottery prizes with the Block Lottos API? Yes. The GET `/api/lottery/check-prizes/{wallet}` endpoint checks a wallet address for winning tickets, and GET `/api/lottery/tickets/{wallet}` lists the tickets that wallet holds, so an agent can report both current holdings and any prizes owed. ### What are the rate limits for the Block Lottos API? The OpenAPI spec does not specify rate limits for the Block Lottos API. Because the lottery data endpoints are read-only, treat them as cacheable and poll draw history and jackpot values on a schedule; check the provider's site at https://blocklottos.com for any stated limits. ### How do I buy a lottery ticket through Jentic? Search Jentic for 'buy a lottery ticket', load the matching operation, and call POST `/api/lottery/build-ticket-tx` to get the unsigned transaction for the user's wallet to sign. To run it on your own infrastructure, install Jentic One from its GitHub repo. ### Can I limit what my agent is allowed to do with the Block Lottos API? Yes. Because Jentic One is self-hosted, you decide which operations the agent may call: you might allow the read-only lottery lookups like GET `/api/lottery/jackpot` and GET `/api/lottery/draw-history` while leaving out ad submission or ticket-transaction building, and every call the agent makes is logged.