Install Jentic One Beta

Connect the Block Lottos API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Block Lottos API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fblocklottos.com%2Fblocklottos" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fblocklottos.com%2Fblocklottos" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Block Lottos API.

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

GET STARTED

Start building with Block Lottos API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Block Lottos API for, with concrete tasks.

★ 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.

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.

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.

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.

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

16 endpoints — the block lottos api reports on-chain lottery draws and runs a self-serve advertising placement flow for the platform.

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

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?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using Block Lottos API through Jentic.

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.

Block Lottos API

Name: Block Lottos API
Brand: Block Lottos API
Availability: InStock

Official vendor OpenAPI document · agent-readyMarketingAdvertisingnone16 EndpointsREST

For 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.

Use for: Get the current Block Lottos jackpot amount, Retrieve the full lottery draw history, Check whether a wallet holds any winning tickets, List the tickets a given wallet has bought

Not supported: Does not handle payment settlement, wallet custody, or identity verification. Use for on-chain lottery data and ad placement submission only.

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.

Jentic One on Github View OpenAPI Document

Connect the Block Lottos API to your agent

Capabilities

Start building with Block Lottos API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Block Lottos API