SEO Domains By Technology
Find websites running a given technology, category, or on-page term: domain, rank, detected stack, contacts, and social profiles as normalized JSON.
Price: billed per result - $12.00 per 1,000 requests base + $1.20 per 1,000 results, capped at $132.00 per 1,000 requests.
Routing: one lane serves this API today, so a failed attempt has nowhere to fail over to. Payment outcome follows the selected rail’s settlement policy.
Catalog: SEO Domains By Technology pricing and uptime - live USD price, lane routing, and measured 30-day uptime. Every Seo endpoint.
Authorizations
Your AnyAPI key as a Bearer token.
Headers
Optional wallet idempotency key, scoped to this customer for 24 hours. When the gateway honors the key, this synchronous in-process execution can continue after the caller disconnects, bounded by its execution deadline. A completed replayable result charges normally exactly once and can be replayed without another provider run or charge. A pending duplicate returns 409 idempotency_in_progress; reuse with different request semantics returns 409 idempotency_conflict.
1 - 255Query Parameters
Optional. Comma-separated keys (dotted paths like author.name descend into nested objects) to keep on each result item. Keys are matched relative to each result item after the data/items envelope is unwrapped, not against the top-level response envelope, so use jq to reshape the whole envelope. Shrinks the response without changing cost.
Optional. Cap the number of result rows returned; a _truncated note reports how many were withheld so you can page via the API's own limit. Does not change cost.
x >= 0Optional. Return only a structural outline (top-level keys, item counts, and per-field byte sizes) instead of the full data. Does not change cost.
Optional. A jq expression applied to the result envelope; its output replaces output (multiple outputs collect into an array). Reshape freely, e.g. jq=.data | {title, description, md: .markdown[:3500]}. Runs sandboxed with a 250ms / 2MB budget; on failure the full result is returned with a jqError. Does not change cost.
Body
- SEO Domains By Technology input
- SEO Domains By Technology input
- SEO Domains By Technology input
- SEO Domains By Technology input
Exact technology name to match, for example Nginx or HubSpot. Only technologies present in the detection index are accepted; an unindexed name returns found false, so use keyword instead when a product is not matched by name.
2 - 100Technology category to match, for example marketing_automation. Broader than technology: it returns every domain running anything in that category.
2 - 100Pagination cursor from a previous response's nextCursor. Omit for the first page.
Top-level technology group to match, for example marketing or servers. The broadest selector.
2 - 100On-page term to match in the site's HTML, for example highlevel. Use this to find sites running a product that the technology index does not detect by name.
2 - 100Maximum number of domains to return in this response. You are billed per returned result, so a lower limit costs less.
1 <= x <= 100Sort order for the returned domains: by domain rank descending or ascending, by most recently crawled, or by country code. Omit for the default order.
rank_desc, rank_asc, last_visited_desc, country_asc Response
Normalized result.
USD charged on the original run. On a replay this value is echoed for parity; the replay itself is free.
Number of result rows returned. For per-result SKUs the per-item cost is charged against this count; for input-priced SKUs the charge is per submitted input, independent of this count.
Normalized output, or null when the replay payload was not retained.
Always "AnyAPI".
True when this response replays the durable result of an earlier run without billing or upstream execution.
Optional one-line nudge, absent when there is nothing to say. large_result: suggests the fields/max_items/summary/jq controls for a big response. paging_unavailable: means this result came from a source that cannot return a nextCursor, so it may be INCOMPLETE and cannot be continued - re-run with requireCursor: true to be served only by a source that can page, which may cost more per request.
Present only when a jq expression failed; output then carries the full unshaped result and this explains why the reshape did not apply.
Opaque handle to the full unshaped result, cached ~15 min. Re-shape it for free (fields/max_items/summary/jq) via GET /v1/results/{id}, no re-billing. Absent when the result was too large to cache.