Introduction
The technographics.ai API returns the technologies a company runs on — frontend, cloud, analytics, CRM, payments and more — from a single domain. It's available as a REST endpoint and as an MCP server for AI agents.
Base URL: https://technographics.ai
Authentication
All requests require an API key. Create one in your dashboard, then pass it as a bearer token:
Authorization: Bearer tg_your_api_key
Keys are shown once at creation. Treat them as secrets — never expose them in client-side code.
Get technographics
GET /api/v1/technographics
Query parameters
domain— required. The company's domain, e.g.stripe.com.
If we've profiled the domain before, the cached profile is returned instantly. If not, a live scan runs (this can take 20–40s) and the result is then cached.
Example request
curl -H "Authorization: Bearer tg_your_api_key" \ "https://technographics.ai/api/v1/technographics?domain=stripe.com"
Example response
{
"domain": "stripe.com",
"company": { "name": "Stripe" },
"technologies": [
{ "name": "React", "category": "frontend", "vendorDomain": "react.dev", "confidence": 95 },
{ "name": "AWS", "category": "cloud", "vendorDomain": "aws.amazon.com", "confidence": 90 },
{ "name": "Cloudflare", "category": "cdn", "vendorDomain": "cloudflare.com", "confidence": 92 }
],
"summary": "Stripe runs a React frontend on AWS behind Cloudflare…",
"generatedAt": "2026-06-20T18:00:00.000Z",
"cached": true
}Response schema
| Field | Type | Description |
|---|---|---|
| domain | string | The normalized domain that was profiled. |
| company.name | string | The company's display name. |
| technologies[] | array | Detected technologies. |
| technologies[].name | string | Canonical product name, e.g. 'Cloudflare'. |
| technologies[].category | string | frontend · cloud · cdn · analytics · crm · payments · … |
| technologies[].vendorDomain | string? | The vendor's website, e.g. 'cloudflare.com'. |
| technologies[].confidence | number | 0–100 detection confidence. |
| summary | string | One-paragraph human summary of the stack. |
| generatedAt | string | ISO timestamp of the profile. |
| cached | boolean | True if served from store; false if freshly scanned. |
MCP server
The same data is available to AI agents over the Model Context Protocol (streamable HTTP). Point your MCP client at:
https://technographics.ai/api/mcp
Authenticate with the same API key (Authorization: Bearer tg_…). The server exposes one tool:
get_technographics(domain)— returns the company's technology profile (same shape as the REST response).
Example client config
{
"mcpServers": {
"technographics": {
"url": "https://technographics.ai/api/mcp",
"headers": { "Authorization": "Bearer tg_your_api_key" }
}
}
}Rate limits & errors
Requests are rate-limited per API key. Exceeding the limit returns 429.
| Status | Meaning |
|---|---|
| 200 | Success. |
| 400 | Missing the domain parameter. |
| 401 | Invalid or missing API key. |
| 422 | The domain is not valid. |
| 429 | Rate limit exceeded. |
| 500 | Enrichment failed. |