Find a company or person by name, URL, or id
Authentication
User bearer token: Clerk session JWT, Clerk OAuth access token, or Clerk API key
Query parameters
Also considers hidden and unpublished records; needs private-visibility authority. Without it, NO_MATCH covers only records you can see.
Treat name only as an exact id, public handle, registry id, or slug: no model call, no web search, and 404 when nothing matches. An exact match never spends the natural-search quota, with or without this flag.
Request
Specific facts in plain words: product, industry, employer and title, or founder names. Generic words like startup add nothing.
City, region, or country, such as Austin, TX. Tells namesakes apart; not proof on its own.
aVenture news id of the article that mentions the subject; an unknown id is a 400.
URL of the article that mentions the subject; read from aVenture news when stored there, otherwise fetched.
URLs the subject owns: its website, its LinkedIn company or person profile, or a registry page. At most 10. Put articles in sourceUrl.
Response headers
Requests allowed per client IP in the current rate-limit window.
Requests left before the tightest applicable rate-limit bucket rejects.
Seconds until the exhausted rate-limit bucket admits another request; 0 when none is exhausted.
Response
The identification as canonical JSON or compact text/plain.
What the caller does next: act on match, create, or ask the user.