Developers

Query the Decision Insights Registry from your own code or your own agent: companies, open source projects, technology terms and dated records, each linked to its primary source.

Quickstart

Pick one. None of them needs an account.

claude mcp add --transport http decision-insights https://mcp.decisioninsights.ai/api/mcp-public

claude mcp add --transport http decision-insights https://mcp.decisioninsights.ai/api/mcp-account

curl "https://api.decisioninsights.ai/api/public/v1/search?q=SASE"

npm i -g @wiretap/decision-insights-cli
di get-company --website netskope.com

Accounts and sign-in

There is no API key to request. With no credential you are served at the anonymous tier. That is supported, not an error.

A free account raises your limits and opens the rest of the REST API and every CLI command. Choose a plan on Pricing, including the free one. Use your work address at your company's domain: the domain attaches the account to your company, so free mailboxes are refused. Then open the link we email you. It verifies the address and signs you in.

Signed in, you send an OAuth access token in an Authorization header: Bearer YOUR_TOKEN. An x-api-key header carrying the token is accepted too. di login and an assistant's sign-in prompt get a token for you. Writing your own client is covered under Signing in over OAuth, below.

Rate limits

Limits are per caller, per minute and per day. They rise when you sign in.

This table is read from the server that enforces the limits, so it changes when they do. Every reply also states yours: X-DI-Tier is the tier you got, X-RateLimit-Limit the per minute ceiling, and X-RateLimit-Remaining what is left.

Over the limit, you get a 429 with Retry-After in seconds. Wait that long before you retry. Paid plans raise the limits: see Pricing.

Common patterns

More calls, each run as shown.

di get-company --website netskope.com

curl https://api.decisioninsights.ai/api/public/v1/companies/edc9173b-5856-41a5-932f-082923f4ecf8

curl -X POST https://mcp.decisioninsights.ai/api/mcp-public \
  -H "content-type: application/json" \
  -H "accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"di_get_company","arguments":{"website":"netskope.com"}}}'

curl "https://api.decisioninsights.ai/api/public/v1/industries?q=SASE"

curl -X POST https://mcp.decisioninsights.ai/api/mcp-public \
  -H "content-type: application/json" \
  -H "accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"di_search_companies","arguments":{"industry":"information-technology/cybersecurity/network-security/sase-sse-zero-trust-network-access","limit":10}}}'

di search-content "SASE" --limit 5

curl "https://api.decisioninsights.ai/api/public/v1/search?q=SASE"

di get-glossary --slug vector-database

curl -X POST https://mcp.decisioninsights.ai/api/mcp-public \
  -H "content-type: application/json" \
  -H "accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"di_get_term","arguments":{"slug":"vector-database"}}}'

claude mcp add --transport http decision-insights https://mcp.decisioninsights.ai/api/mcp-public

{
  "mcpServers": {
    "decision-insights": {
      "command": "npx",
      "args": ["mcp-remote", "https://mcp.decisioninsights.ai/api/mcp-public"]
    }
  }
}

Base URL

https://api.decisioninsights.ai/api/public/v1

Endpoints

With no account, /search, /companies/{uuid} and /industries answer. The rest need a free account, signed in. Each takes a required query parameter, and a request without it returns a 400 naming the one that is missing.

/companies looks a company up by its own domain. With a keyword instead, use /search.

Beyond the obvious fields: a company record lists the open source projects it owns as projects, with projects_total and projects_truncated saying when the list is a subset. A content record lists the companies the article mentions as mentioned_companies, each with the @id its own record publishes, plus mentioned_companies_total, mentioned_companies_truncated and mentions_extraction. That last one says mentions come from automated name extraction and may include false positives. A content record also carries subject_company_id, project_refs and canonical_url. A project record names its owning company as owner_organization_id, an identifier you can dereference.

The same endpoints are described as OpenAPI at https://decisioninsights.ai/openapi.json, so a client can generate itself.

Endpoints that act on your account

These need an access token and work on your own account.

Watch lists follow a set of companies. Webhooks notify you instead of making you poll. If your account reaches more than one organization, add ?organizationUuid= to say which. A request that leaves it ambiguous returns a 403 listing the ones you can choose.

Signing in over OAuth

For anyone writing their own client. Three cases, and they differ. No Authorization header: served at the anonymous tier. A header we cannot recognise: 401 invalid_token, naming what arrived and what we accept. A token we could not check because our identity service was unreachable: served at the anonymous tier, so the request still succeeds.

Tokens are issued by https://my.decisioninsights.ai. Its metadata is at https://my.decisioninsights.ai/.well-known/oauth-authorization-server, so a client can configure itself. This site's resource metadata, at https://decisioninsights.ai/.well-known/oauth-protected-resource, names that issuer.

The MCP endpoint is a separate resource with its own metadata, at https://mcp.decisioninsights.ai/.well-known/oauth-protected-resource. It names the same issuer. Follow the authorization_servers in the document for the resource you are calling. One credential works for both.

Registering a client

You do not need to ask us. POST https://my.decisioninsights.ai/oauth2/register is dynamic client registration (RFC 7591). It takes no credential and is rate limited. Send client_name, redirect_uris and token_endpoint_auth_method. A command line tool or desktop app should send none and keep no secret: PKCE is the proof instead, and only S256 is accepted.

Redirect URIs must match exactly, so register every one you might use, each loopback port included.

Which grant you get

authorization_code is what a self-registered client always gets. A person signs in once in a browser, the token comes back to your redirect URI, and it renews itself with refresh_token. That is the grant behind di login and an assistant's sign-in prompt. The scope is profile, which is what reading the registry needs.

client_credentials is in the metadata, but you cannot self-register into it. It is for a first-party service acting on a whole account, so those clients are created by hand. A registration that asks for it is still created as an authorization code client, so read grant_types in the response. If you need one, talk to us.

The authorization server serves other products too, and its metadata lists their scopes beside profile. A self-registered client cannot hold them.

Command line

The CLI is @wiretap/decision-insights-cli on npm. It installs a command named di and needs Node 18 or newer. Each command is one MCP tool call, so it returns the same records as the API and MCP. With no account it runs the search commands, get-company and list-industries. The rest need a free account: di login signs you in and raises your limits to your plan's.

MCP

The same data is served over MCP at two addresses, with the same tools. https://mcp.decisioninsights.ai/api/mcp-public is the anonymous version: no account, no sign-in, anonymous limits. The address for your account, Free or paid, is in the Quickstart above: sign in once and your plan's limits apply, and upgrading never changes the URL. To set up an assistant, with a block for each client and the ten tools, see Agents & MCP.

Attribution

Every record carries the link to its primary source. If you surface a record, carry that link with it.