KAKUDO / DEVELOPER PLATFORM

Reliable context
for your product.

Use the same read-only Stock Token signals that power Kakudo. Public endpoints expose market and event facts. Private wallets and positions stay out of the public API.

Open developer workspace OpenAPI specification

Public API

Start with JSON endpoints. Use symbols to narrow a request. Each response includes a fetch time and source status.

GET /api/v1/risk-feed?symbols=AAPL,NVDA

Integration keys

Create server-side keys in your workspace for recorded usage and managed access. Keep secrets off the client.

Manage keys

Signed webhooks

Corporate-action webhooks use a separate operator key during the current release. Receivers must verify each signature and deduplicate event revisions.

Read webhook boundary

REFERENCE

Endpoints

Responses are advisory and never execute transactions. Public dependency discovery describes venue coverage, not a user's personal exposure.

GET/api/v1/catalogStock Token catalog and contract metadata GET/api/v1/risk-feed?symbols=AAPL,NVDAEvent and market risk context for selected assets GET/api/v1/quote-integrity?symbols=AAPLMultiplier, halt and quote freshness checks GET/api/v1/dependencies?symbols=AAPLSupported public protocol markets; never personal positions GET/api/v1/events?symbols=AAPLOfficial corporate action records GET/api/v1/assets/AAPLMetadata and current context for one token GET/api/v1/openapi.jsonMachine-readable OpenAPI description POST/api/v1/webhooksOperator-managed signed event webhooks

Integration boundary

Use Kakudo to detect and explain. Confirm source records before trading or changing protocol parameters. The API, MCP tools and webhooks do not expose private wallet scans and do not submit transactions.

Read source and coverage guide