Technology taxonomy for AI agents

Scope and access

An open software technology taxonomy for people, applications and AI agents, maintained by Queast. 1467 technology records; selected approved release 2026.10.7, schema 1.2.1, dataset license CC-BY-SA-4.0. Optional aliases, descriptions, classifications, relationships and sources are available only when included in the release.

Taxonomy facts belong to the selected immutable release. Separately fetched Queast job-ad demand is live enrichment, not adoption or market share.

Identity and missing matches

Retain canonical IDs across systems. Resolve names and available aliases before proposing new identities. Inspect ambiguity and missing matches; do not treat a failed match as proof that a technology does not exist. Search candidates and inspect their detail, lifecycle and sources before choosing a match.

Use category_ids and domain_ids to join the released classification lists. Relationships connect canonical IDs through explicit types; parent_of is the primary technology hierarchy, separate from category nesting.

Search, resolve and detail

Release-derived example input: "JavaScript". Expected identity when unambiguous: tech_000000000000009YBMQKJJXTT7 (JavaScript). Search may return several candidates; an exact resolution may be ambiguous or missing. Never accept a candidate solely because it appears first.

Search and exact name/alias resolution use the active release. Fetch detail by canonical ID, then read /api/v1/technology-relationships/{canonicalID} for typed edges. MCP tools search_technologies, resolve_technology, get_technology and list_related_technologies provide the same application services.

curl --fail-with-body 'https://technologies.quea.st/api/v1/technologies?q=JavaScript&limit=25'

curl --fail-with-body 'https://technologies.quea.st/api/v1/technology-resolutions?name=JavaScript'

curl --fail-with-body 'https://technologies.quea.st/api/v1/technologies/by-id/tech_000000000000009YBMQKJJXTT7'

Transport and citations

GET /api/ and GET /mcp/ are human documentation pages. POST /mcp is the JSON-RPC MCP transport (protocol 2025-06-18); an ordinary GET does not call a tool. Anonymous API and MCP reads share rate limits; respect Retry-After.

Cite the canonical record URL and the dataset release. The API uses the active release and does not offer version pinning. For reproducibility, download the immutable versioned JSON, verify its SHA-256 and retain version, schema and checksum. The dataset license does not license third-party technologies, trademarks, source prose or application code.