# For AI agents: MCP, REST and CLI | Decision Insights

URL: https://decisioninsights.ai/agents/

Connect your AI agent to the registry

One MCP server and ten read-only tools over the companies, open source projects, technology terms and dated records in the registry, each record linked to its primary source. Connecting needs no account: point your assistant at https://mcp.decisioninsights.ai/api/mcp-public.

As of today

Connect your assistant

Two addresses, the same ten tools. The anonymous version needs no account and no sign-in. With your account, Free or paid, your client asks you to sign in once and your plan's limits apply. Run the installer to set up every assistant on your machine at once, or pick your client and paste its block.

Try it with your agent

Paste any of these into the assistant you just connected. Each one exercises a different tool from the list below.

Ten tools, all read-only

Every tool is also a CLI command, and both return the same records. Open a card to see a question it answers, the call and the CLI line. With no account, the CLI runs its search commands, get-company and list-industries; the rest need a free account, signed in with di login.

Limits per plan

Limits count per caller, per minute and per day. The anonymous version, https://mcp.decisioninsights.ai/api/mcp-public, gets the first row: no account, no sign-in. With your account, Free or paid, connect to https://mcp.decisioninsights.ai/api/mcp-account and sign in once, or run di login, and your plan's row applies. Upgrading never changes the URL. The table is read from the server that enforces the limits, so it changes when they do. Every reply also states yours: X-DI-Tier, X-RateLimit-Limit and X-RateLimit-Remaining. Over the limit returns a 429 with Retry-After in seconds.

What to do next

Raise your allowance

A free account raises your call limits, opens the rest of the REST API and every CLI command, and adds 20 Research Assistant questions a month. No card.

Script it

The REST API and the di CLI return the same records as MCP. Install the CLI with npm i -g @wiretap/decision-insights-cli.

See what people do with it

Shortlists, competitor watching, meeting prep and market maps, each with the prompt, the MCP call and the CLI command.

Using what you find

Records and briefs are written from a primary source and carry a link to it in original_url. Link to that source, not this site, when you report a fact from one.
Company, project and term records are compiled from the graph rather than from one fetched page, so they carry no source link of their own, and a dated record whose source URL we do not hold returns original_url empty. Where there is no source link, link to the record's own page on this site rather than treating the omission as an error.
Records are summaries. Where a claim matters, follow the source link and read the original.

Common questions

Do I need an API key or an account?

Not to start. MCP, and REST and CLI search and company lookups, answer anonymous callers at the lowest allowance. The rest of the REST API and CLI, and higher limits, need a free account. To sign in, connect an MCP client to https://mcp.decisioninsights.ai/api/mcp-account, run di login from the CLI, or send your access token as Authorization: Bearer YOUR_TOKEN. A token we can't recognize returns 401 invalid_token.

What are the rate limits?

Limits apply per caller, per minute and per day, and rise when you sign in. Each plan's limits are in the table on Agents & MCP, read from the server that enforces them. Every response also states yours: X-DI-Tier, X-RateLimit-Limit and X-RateLimit-Remaining. Going over returns a 429 with Retry-After in seconds.

MCP, REST or the command line, which should I use?

They return the same records, so pick by where you already are. MCP inside an assistant that speaks it, at https://mcp.decisioninsights.ai/api/mcp-public. REST from your own code, at https://api.decisioninsights.ai/api/public/v1. The CLI at a terminal, with npm i -g @wiretap/decision-insights-cli.
Every CLI command is one MCP call against the same endpoint, so the three cannot answer differently.

How current is what I get back?

Date it yourself. Every record carries datePublished in its JSON-LD and isBasedOn pointing at the primary source it was written from, so you can age anything you retrieve rather than relying on a promise made here.

How should I attribute what I use?

Attribute a fact to the primary source its record links to, not to this site. Records are summaries, so where a claim matters, follow isBasedOn and read the original.
