Daawid's REST API

The same answers as Daawid's MCP server, over plain HTTP: search the registry, read entries, and start requests to the businesses and people that take them.

Its address, and a first call:

https://api.daawid.com/v1

curl "https://api.daawid.com/v1/search?q=plumber&place=Wuppertal"

Reading is free

Searching and reading cost nothing and need no key or sign-in. Every caller gets the same results in the same order. Answers are JSON.

How Daawid orders search results

Routes

Every route, parameter and answer, as an OpenAPI 3.1 file

Sending a request

An entry's actions say which requests it takes. Each has its address (rest) and what it asks for (inputSchema). The body names the entry in entry and holds the input of the action's kind.

Nothing is sent when you call it. The answer's confirmUrl is Daawid's page, where the person checks what goes to whom, types the code Daawid emails them and presses Send. Give them that link. With an Idempotency-Key header, the same call within 24 hours is the same request, not a second one.

Errors

Errors are RFC 9457 problems (application/problem+json), with the same codes as the MCP server's in code, and what went wrong in detail.

Limits

300 reads a minute per client and IP address. Requests have limits of their own, per entry and per email address, and none per IP address.

What Daawid counts

Each entry returned counts as a read of it, and each search stays in Daawid's log for 30 days: what was asked and found, and the AI company whose app asked, if the user agent names one. Nothing ties a call to a person.

Daawid's privacy policy

Where places come from

From the open data of GeoNames (https://www.geonames.org): towns of 500 people or more, with their names in many languages, and postal codes in over 120 countries, under the Creative Commons Attribution 4.0 licence (https://creativecommons.org/licenses/by/4.0/). Daawid has turned them into an index of its own.

Daawid in your AI app