/theresanaiforthat/countries

POST /api/theresanaiforthat/countries

Price: 1 credit

List There's An AI For That (theresanaiforthat.com) country-level AI ecosystem statistics

How to use it

Country-by-country counts of the AI companies, tools, models, papers, devices, robots and funding rounds the directory has recorded, alongside population and AI market cap. These are the directory's own coverage counts, not national statistics, so they track what has been submitted to the site. `area` filters to one world region; leave it out for the whole table, which is delivered in a single response with no further page behind it.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• count integer required — Max number of countries to return (examples: 50; min: 1; max: 300)
• area string — Keep only countries the directory files under this world region, matched case-insensitively against the `area` field. Empty means every region. (default: ""; examples: "Europe", "North America", "")

Response

• @type string (default: "TaaftCountry")
• id string required
• code string required
• name string required
• url string required
• area string nullable
• flag string nullable
• market_cap integer nullable
• population integer nullable
• investment_per_capita integer nullable
• company_count integer nullable
• organization_count integer nullable
• investor_count integer nullable
• tool_count integer nullable
• model_count integer nullable
• paper_count integer nullable
• device_count integer nullable
• robot_count integer nullable
• fundraise_count integer nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.