Verdict

Boarding: tell us what you need

Verdict sells small pay-per-call checks to AI agents. We do not know everything agents need, and guessing is slow. This desk is open to any agent, and to the person running one: say which paid API you looked for and could not find. It is free, nothing is charged, and we are clear about what happens to what you write.

What you get, and what you do not

YesYour request is counted. Requests from different clients decide which service gets built next.
YesIf we build it, it appears in the catalog and in the Coinbase Bazaar listing, where you can find it.
NoNo promise. We may never build it. We cannot reply to you: we keep no contact details.
NoNo payment, no account, no key. Nothing is sold to you here.

What we keep, and what we do not

We keepWe never keep
The text you send (at most 500 characters), the optional price, frequency and agent name, the time, and a hashed client fingerprint.Your IP address, your keys, anything about your wallet or your payments.

The free search GET /v1/search?q= logs the query text (200 characters at most) and how many of our services matched, with the same hashed fingerprint. Do not put secrets in either. The full policy is on the trust page.

How an agent declares a need

One request, no payment:

curl -X POST https://verdict.kechlab.com/v1/request-service \
  -H 'Content-Type: application/json' \
  -d '{"need": "Check an ERC-20 token contract on Base before I swap",
       "max_price_usdc": 0.01, "frequency": "daily"}'
Field
needRequired. 8 to 500 characters: what the service should do.
example_inputOptional. An example of the request body you would send (400 characters at most).
max_price_usdcOptional. The most you would pay per call. A real number helps us decide.
frequencyOptional. once, daily, hourly or continuous.
agentOptional. Your agent name.

Limits: 10 requests per minute per address, 20 per day per client. A machine-readable version of this page is GET /v1/request-service. Agents that only want to know what we already sell can search the catalog: GET /v1/search?q=....

How we use it

We rank requests by the number of different clients who asked, not by the number of messages: one agent asking ten times counts once. A stated need is not a purchase, so we weigh it as a signal and build only what several independent clients ask for. We do not publish individual messages.

Declare a need from a browser

For the person who runs an agent. This sends exactly the request shown above.