/theresanaiforthat/companies

POST /api/theresanaiforthat/companies

Price: 20 credits

Get There's An AI For That (theresanaiforthat.com) AI company profile by slug or company URL

How to use it

Company profile behind AI tools listed in the directory — headquarters, funding, headcount band, directory rankings, and the company's own tools inline. An unknown slug is rejected rather than answered with a near match. `valuation`, `raised` and `employee_count` arrive as the directory renders them ('$852B', '4.5k'), not as numbers. `company_alias` from /theresanaiforthat/tools is the input this endpoint expects.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• company string required — There's An AI For That company slug ('openai') or full company URL ('https://theresanaiforthat.com/company/openai/'). (examples: "openai", "https://theresanaiforthat.com/company/anthropic/"; minLength: 1; pattern: ^(?:https?://[^\s]+|//[^\s]+|(?:www\.)?theresanaiforthat\.com[^\s]*|/?[A-Za-z0-9][A-Za-z0-9._+%-]*/?)$)

Response

• @type string (default: "TaaftCompany")
• id string required
• alias string required
• name string required
• url string required
• description string nullable
• website_url string nullable
• industries array (default: [])
• location string nullable
• country_code string nullable
• is_ai_native boolean nullable
• is_profitable boolean nullable
• employee_count string nullable
• valuation string nullable
• is_valuation_estimated boolean nullable
• raised string nullable
• tool_count integer nullable
• model_count integer nullable
• most_popular_tool string nullable
• most_popular_tool_alias string nullable
• ranks array (default: [])
  • @type string (default: "TaaftCompanyRank")
  • label string required
  • position integer required
• social_links array (default: [])
• tools array (default: [])
  • @type string (default: "TaaftToolSummary")
  • id string required
  • alias string required
  • name string required
  • url string required
  • tagline string nullable
  • icon string nullable
  • website_url string nullable
  • website_domain string nullable
  • task string nullable
  • task_id string nullable
  • task_alias string nullable
  • country string nullable
  • released string nullable
  • latest_release string nullable
  • modality string nullable
  • pricing string nullable
  • trending_rank integer nullable
  • view_count integer nullable
  • save_count integer nullable
  • rating number nullable
  • match_labels array (default: [])
  • is_verified boolean nullable
  • is_promoted boolean nullable
  • is_gpt boolean nullable
  • is_mini_tool boolean nullable
  • is_unavailable boolean 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 — Company not found 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.