StackologyIn build

Tools don’t have to work alone.We map how they connect.

A verified map of how software connects (integrations, APIs, MCP servers, webhooks), sourced from the vendor’s own pages and built for AI agents to query.

01 · The map
Fig. 01 · Illustrative graph
NativeMCPAPIWebhook
Illustrative map of software connectionsrelay → acme (api); acme → relay (webhook); acme → northwind (native); kestrel → acme (mcp); fabrikam → acme (mcp); acme → harbor (webhook); relay → northwind (api); relay → fabrikam (api); quill → orbit (api); tessel → relay (webhook); lumen → relay (mcp); orbit → northwind (webhook); parcel → harbor (api)Acme LedgerTOOLNorthwind MailTOOLFabrikam CRMTOOLRelay HooksCONNECTORQuill DocsTOOLOrbit CalendarTOOLKestrel ChatTOOLLumen BridgeCONNECTORTessel FormsTOOLHarbor StoreTOOLParcel SyncCONNECTORE·01Illustrative map of software connectionsrelay → acme (api); acme → relay (webhook); acme → northwind (native); kestrel → acme (mcp); fabrikam → acme (mcp); acme → harbor (webhook); relay → northwind (api); relay → fabrikam (api); quill → orbit (api); tessel → relay (webhook); lumen → relay (mcp); orbit → northwind (webhook); parcel → harbor (api)Acme LedgerTOOLNorthwind MailTOOLFabrikam CRMTOOLRelay HooksCONNECTORQuill DocsTOOLOrbit CalendarTOOLKestrel ChatTOOLLumen BridgeCONNECTORTessel FormsTOOLHarbor StoreTOOLParcel SyncCONNECTORE·01A1A9F1F9
Edge · illustrative

Acme Ledger → Northwind Mail

E·01 · native · source_to_dest
Mechanism
Native integration
acme.example/integrations/northwind · captured 16 Oct 2026
Direction
source_to_dest
docs.acme.example/integrations/northwind#sync · captured 16 Oct 2026
Data
Produces: invoices · Consumes: contacts
docs.acme.example/integrations/northwind#data · captured 16 Oct 2026
Auth
OAuth 2.0
docs.acme.example/integrations/northwind#auth · captured 16 Oct 2026
Plan required
Business and above
acme.example/pricing · captured 16 Oct 2026
Operations
6 documented
docs.acme.example/integrations/northwind#operations · captured 16 Oct 2026

We are charting the software economy one vendor at a time. This is the shape of it. Illustrative.

Fictional names · .example domains
02 · What the map holds

Nodes

Tools and connectors, each one a record built from its vendor’s pages.

Edges

Every connection between two nodes, typed by kind and drawn in the direction data moves.

docs.vendor.example/line

Citations

Every value traces back to the exact line on the vendor’s own page it came from.

03 · How it is verified

Facts, not estimates.

  1. 01

    Read only the vendor’s public pages.Never third parties, never reviews.

  2. 02

    Cite the exact line each value comes from.

  3. 03

    Published facts only.If the vendor hasn’t said it, neither have we.

  4. 04

    Verified at the source.Cited to the line.

Nothing reaches the map without all four.How we verify →
04 · Access

Built for agents

Query it over MCP. Pay per query. No account to start.

Building/mcp →

Vendors

Get your product’s connectivity on the map, from your own pages, at no cost.

/vendors →