Skip to main content

Developer API Overview

What the Developer API is​

The Cognivo Developer API lets you call the same on-chain intelligence that powers Cognivo Chat, the dApp and the Telegram bot from your own code. You create a project, create an API key, and send requests over plain HTTPS.

  1. The Developers area is where you create projects and manage your Cognivo API keys.
  2. Select Sign in to open the developer portal. Your keys stay private to your account.
The Developers page in the Cognivo dApp.Enlarge image

When to use it​

Use it when you want Cognivo answers inside something you are building rather than inside Cognivo. Common cases:

  • A community bot where someone pastes a contract address and gets back risk signals, liquidity and lock context, and a read on why a token is down.
  • A monitoring dashboard for a treasury, team or whale wallet: approval exposure, recent movements, realized profit and loss per token.
  • A research notebook that pulls token and wallet data into Python or JavaScript for a study or a post mortem.

It is not raw node or RPC access. You always call curated Cognivo endpoints. There is no trading, order execution or MEV tooling. Results are intelligence signals, not financial advice, and a clean result never means a token is safe.

Where to find it​

In the dApp, open the sidebar, then Account, then Developers. The direct link is dapp.cognivolabs.io/en/developers. You need to be signed in with your normal Cognivo account. Signed out, the page shows an orientation screen only, with no projects or keys.

The top of the Developers page in the dApp, where you find the base URL and how to send your API key.Enlarge image

The card at the top of the page carries the three things you need to make a first call:

  • Base URL: https://api.cognivolabs.io. Add an endpoint path to it to make a request.
  • Auth: send your API key in the X-API-Key header on every request. Keep the key on your server, never in browser code.
  • Chains: the page shows Ethereum, Base, and BSC live, and More chains coming soon. Some endpoints support fewer chains than others, and the Endpoint reference says which.

The same card links to these docs and to the machine-readable OpenAPI spec, which you can import into Postman, Insomnia or an SDK generator.

The page itself has four tabs: Quickstart, Keys, Endpoints and Usage. Endpoints is a reference with copyable examples and the price of each call. There is no live runner on the page, so nothing you read there spends anything.

Access, keys and cost​

Live keys are self-serve. Create one and it works right away, with no application and no approval queue. The portal states the model plainly: some endpoints are free with any active key, and others need paid or Enterprise access and are charged per successful call from your Cognivo credit balance.

  • Live keys (cogv_live_) make real calls. Each successful call is charged in Cognivo credits at the price published for that endpoint. Failed calls are never charged. Charging for Developer API calls is switched off today, so a successful call deducts nothing and your balance does not move.
  • Test keys (cogv_test_) are labelled Test in the portal. They have tight limits and are for trying the API out, not for real traffic.
  • Every key shows its access mode on the Keys tab, such as Paid, Trial, Partner, Sandbox, Enterprise or Request access. A key in Request access has to be approved before it can run the paid endpoints, and a Suspended key cannot call anything. The portal shows the reason.
  • Enterprise is the only path where you request access, for custom pricing and limits. The Enterprise access button opens the support flow.

Credits come from the same balance you use everywhere else in Cognivo, and every account gets 5 free credits per day that reset at midnight UTC. If your balance cannot cover a call you get a 402 error with the code payment_required, and nothing is charged. Top up and try again. See Billing and credits for how the balance works.

GET /v1/api/health is free and needs no key. GET /v1/api/me is free with any valid key. GET /v1/api/discover is free with a tight daily cap. Per-endpoint prices are on the Endpoint reference and Rate limits, errors and billing.

What comes back, and what a blank answer means​

Responses carry public on-chain intelligence only. They never include Cognivo account identifiers, emails, balances or other private account data, yours or anyone else's. The one exception is GET /v1/api/me, which reports the calling key's own credit balance so you can watch your spend.

An empty field or an unknown value means Cognivo could not verify that item for this token or wallet on this chain. It does not mean the item is absent, and it does not mean the subject is clean. Treat a missing result as unverified, and use the request ID in the response if you need to follow it up.

Next steps​

  1. Sign in and create a project, then create a live key. The full key is shown once, so copy it immediately.
  2. Run your first call with the Quickstart.
  3. Read Authentication and API keys for permissions, rotation and key safety.