Frequently Asked Questions

Open your company in the directory and use Claim this profile, which starts an account. Claiming is free.

A company counts as claimed once there is a subscription against it, free or paid. That is the same fact the profile page itself states, which is why a page you have claimed says you manage it.

Someone with an email address at the domain the company publishes from. The domain is what attaches the account to the company, so a personal mailbox is refused on this path: it would attach the account to the mailbox provider instead.

The form files a request and a person reads it and replies to the address you gave. The page itself answers nothing about your company, deliberately, so the confirmation is the same sentence whatever we hold.

No turnaround is promised, because a page cannot commit whoever opens the queue that week. Asking twice about the same domain does not create a second request; it is added to the one already open.

If you have claimed the profile, edit it from your account.

Otherwise the correction route for any record is the one on Standards and Methodology, which is also where the sourcing rules and the named editorial oversight are.

No. The endpoints answer an anonymous caller, counted rather than refused, at the lowest allowance.

There is no key to copy. Signing in raises the allowance and it is done over OAuth: point an MCP client at https://mcp.decisioninsights.ai/api/mcp-public?auth=oauth and the server challenges instead of serving you anonymously, run di login from the CLI, or send the access token in an Authorization header as Bearer YOUR_TOKEN.

They apply per caller, per minute and per day, and they rise when you sign in. An anonymous caller gets 10 a minute and 50 a day today.

Do not take that from this page. The allowances are retuned without a deploy, so read what you got off the reply: every response carries X-DI-Tier, X-RateLimit-Limit and X-RateLimit-Remaining. Over the limit returns a 429 with Retry-After in seconds.

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 decision-insights-cli.

Every CLI command is one MCP call against the same endpoint, so the three cannot answer differently.

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.

Cite the primary source a record links to, not this site, when you report a fact from it.

Records are summaries. Where a claim matters, follow isBasedOn and read the original.

Three kinds of thing: a technology term, a company, or an open source project or standard.

If it is your own company, use For Companies instead. This page is for telling us about something else.

Something real, in the four markets this site covers: cybersecurity, data centers, network operators, and AI infrastructure. Everything is reviewed before it is admitted, and checked against the rest of the graph rather than on its own.

A glossary term qualifies when it is already in use across those markets, not because one vendor has coined it for one product.

It is filed into a queue a person reads, and they reply by email.

If you name something we already publish, you are told which entry it is and where to read it straight away, without waiting for the reply.

No turnaround is promised. The reply comes from whoever opens the queue, and a page cannot commit them to a date on their behalf.

Yes, so we can reply to you.

Asking to have your own company listed does not need one. That is For Companies, and it takes a domain and an email address and nothing else.