Code it, query it, browse it, or sync it to your CRM. One dataset — tech stacks, vendor maps, partner ecosystems — everywhere your agents and people need it.
REST API, native MCP, a no-code web app, and CRM enrichment. Same intelligence underneath, metered on one shared credit system.
A standard REST interface. Look up any company and pull its full technology, vendor, and partner profile with detection evidence attached.
Trace speaks the Model Context Protocol. Your AI agents query tech stacks, vendors, and ecosystems as a native data source — no glue code.
Search, Overlaps, Trace Agent, and Saved Lists in a no-code interface. Explore the graph and export account lists without writing a line.
Push tech-stack and ecosystem data straight onto your HubSpot and Salesforce records, kept current on the same refresh loop.
Coming soonThe Trace API is a standard REST interface. Look up any company by domain, retrieve its full technology profile, vendor relationships, and partner ecosystem. Filter by specific technologies or ecosystem membership — every response carries detection evidence, so you can validate the data programmatically.
GET /v1/companies/{domain}Full profile: tech + vendors + partnersGET /v1/companies/{domain}/signalsRecent change signalsGET /v1/companies/{domain}/partnershipsPartner ecosystem mapPOST /v1/searchFind companies by technology or ecosystemPOST /v1/enrichBatch enrichment# Full company profile $ curl https://api.tracedata.ai/v1/companies/stripe.com \ -H "Authorization: Bearer $TRACE_KEY" { "domain": "stripe.com", "technologies": [ { "name": "React", "confidence": 0.95 } ], "vendors": [ { "name": "AWS", "source": "subprocessor" } ], "partners": [ { "name": "Xero", "type": "integration" }, { "name": "NetSuite", "type": "integration" } ] }
Trace speaks the Model Context Protocol from day one. Agents built on Claude, Cursor, or any MCP-compatible framework query tech stacks, vendors, and ecosystems as a native data source. OAuth 2.1, no middleware, no glue code.
// Agent receives a question user: "Who does notion.so partner with?" // Agent invokes the Trace MCP tool → tool: "trace.ecosystem.get" domain: "notion.so" // Trace returns a structured signal { "partner_count": 85, "top": ["Slack", "Zapier", "GitHub"], "recent": { "name": "Figma", "month": "2026-02" } }
Most providers make you build custom integrations and parse their responses for your agent. With Trace, the agent just asks — and gets structured signals it can reason over, not rows to scrape.
MCP queries consume credits like API calls. Your agents can also flag suspected inaccuracies through MCP, triggering the same AI-driven accuracy feedback loop.
Trace plugs into the agents and tools your team already runs — query it from any MCP client, or push data straight into your stack.
Query the Trace graph natively from Claude over MCP.
Give ChatGPT live company intelligence via MCP.
Pull tech-stack and partner data into Cursor.
Answer company questions with Trace data in Perplexity.

Bring Trace intelligence into Gemini over MCP.
Sync tech-stack and ecosystem data into HubSpot records.
Enrich Salesforce accounts with Trace tech and partners.

Get Trace change signals delivered in Slack.
Pipe the Trace dataset straight into Snowflake.
Drop Trace company profiles into Notion.
Trigger Zapier workflows on Trace signals.
Add company context to Intercom conversations.

Feed Trace's company graph to Mistral agents.
Add tech-stack context to Zendesk tickets.
Whether you call the API, query via MCP, export from the app, or sync to your CRM, it all runs on the same credits. Pick the plan, pick the method, and spend however makes sense for your team.