Preparing page

Loading product graph, proof, and adoption context.

Preparing tokens&

Loading the next builder or enterprise surface.

Get proof pilot

Revenue API docs

Integrate the verified developer adoption graph.

Track activation events, map account demand, read public adoption data, and give AI agents a stable contract for building on Tokens& without leaking private developer data.

Create tracking key Request proof pilot

First safe call

Dry-run one activation event

curl -X POST https://tokensand.com/api/usage/track/dry-run \
  -H "Authorization: Bearer tk_live_xxx" \
  -H "Content-Type: application/json" \
  -d '{
    "event_name": "FIRST_API_CALL",
    "event_family": "activation",
    "developer_id": "dev_123",
    "email": "builder@company.com",
    "product": {
      "id": "acme-api",
      "name": "Acme API",
      "type": "api",
      "version": "2026-05"
    },
    "account_domain": "company.com",
    "source": "SDK",
    "occurredAt": "2026-05-15T18:00:00.000Z",
    "idempotencyKey": "evt_123"
  }'

Enterprise implementation

Create a company tracking key, dry-run events, batch production usage, and export account action lists.

Open Revenue API setup

Builder and public graph

Read privacy-safe adoption rows for tools, categories, proof pages, rankings, and agent-citable context.

Read public graph

AI coding agents

Use llms.txt plus the dry-run endpoint so Codex, Claude, ChatGPT, and internal agents can generate valid payloads.

Open llms.txt

Activation tracking

Capture docs, SDK, API, workflow, campaign, credit, event, and agent usage as one adoption contract.

Account demand

Map developer activity to account domains so DevRel, growth, and sales can act on verified intent.

Board-ready proof

Turn retained usage, campaign ROI, and category signals into exports, webhooks, and proof reports.

Privacy boundary

Public output is aggregate. Private workspace data stays scoped. Raw developer resale is not the product.

Enterprise integration quickstart

From tracking key to revenue evidence in five steps.

This is the path an implementation engineer or AI coding agent should follow before custom work: prove the payload, send activation, map account domain, then export account/action evidence.

1. Create tracking key

Generate a company-scoped key in Revenue API setup. Keep it server-side and rotate it if it leaves your control.

2. Dry-run event

Send one event to /api/usage/track/dry-run and fix validation issues before production storage.

3. Send activation and retention

Track first successful usage, repeated usage, campaign source, product, and account domain.

4. Map account demand

Use account_domain so Tokens& can create account-level intent, ROI, and expansion evidence.

5. Export to revenue workflows

Push CSV, webhook, report, or CRM-ready action lists once evidence is approved for use.

REST API

A small endpoint set with a clear business job.

Start with the endpoints that create revenue-grade proof: validate, store, batch, read public adoption, and give agents a stable ranking contract. Keep custom integrations behind this same event model.

POST

/api/usage/track/dry-run

Validate payload shape, required identifiers, and account mapping without storing the event.

Tracking key

Implementation engineer

POST

/api/usage/track

Store one activation, retention, commercial, or expansion event for a company product.

Tracking key

Product or SDK team

POST

/api/usage/track/batch

Store up to 500 events from batch jobs, warehouses, CDPs, campaign imports, or event platforms.

Tracking key

Data or RevOps team

GET

/api/v1/adoption

Read public, privacy-safe adoption rows for tools, categories, proof, and rankings.

Public, rate-limited

Builders and agents

GET

/api/v1/agent-rank

Read the public adoption score contract for agent search, recommendation, and citation flows.

Public, rate-limited

AI agents

Copy-paste examples

One event contract from app code, scripts, CDP payloads, or agents.

Include account_domain, campaignId, product, and idempotencyKey. Those fields turn raw events into attribution, account demand, exports, and executive proof instead of another analytics table.

Node / TypeScript

await fetch("https://tokensand.com/api/usage/track", {
  method: "POST",
  headers: {
    "Authorization": "Bearer tk_live_xxx",
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    event_name: "FIRST_API_CALL",
    event_family: "activation",
    developer_id: "dev_123",
    email: "builder@company.com",
    account_domain: "company.com",
    source: "SDK",
    campaignId: "cmp_launch_001",
    product: { id: "acme-api", name: "Acme API", type: "api" },
    idempotencyKey: "evt_123"
  })
});

Python

import requests

requests.post(
  "https://tokensand.com/api/usage/track",
  headers={
    "Authorization": "Bearer tk_live_xxx",
    "Content-Type": "application/json"
  },
  json={
    "event_name": "FIRST_API_CALL",
    "event_family": "activation",
    "developer_id": "dev_123",
    "email": "builder@company.com",
    "account_domain": "company.com",
    "source": "SDK",
    "campaignId": "cmp_launch_001",
    "product": {"id": "acme-api", "name": "Acme API", "type": "api"},
    "idempotencyKey": "evt_123"
  }
)

Segment/PostHog-style payload

{
  "type": "track",
  "event": "FIRST_API_CALL",
  "userId": "dev_123",
  "properties": {
    "event_family": "activation",
    "account_domain": "company.com",
    "product_id": "acme-api",
    "product_name": "Acme API",
    "campaignId": "cmp_launch_001",
    "source": "docs"
  },
  "context": {
    "traits": {
      "email": "builder@company.com"
    }
  }
}

Dry-run curl

curl -X POST https://tokensand.com/api/usage/track/dry-run \
  -H "Authorization: Bearer tk_live_xxx" \
  -H "Content-Type: application/json" \
  -d '{
    "event_name": "FIRST_API_CALL",
    "event_family": "activation",
    "developer_id": "dev_123",
    "email": "builder@company.com",
    "product": {
      "id": "acme-api",
      "name": "Acme API",
      "type": "api",
      "version": "2026-05"
    },
    "account_domain": "company.com",
    "source": "SDK",
    "occurredAt": "2026-05-15T18:00:00.000Z",
    "idempotencyKey": "evt_123"
  }'

Event contract

Send the event name humans use. Map it into a family agents can reason about.

Every event needs an event name and one developer identifier. Organization keys should also send a product descriptor so adoption can be separated by API, model, SDK, workflow, agent, event, or docs surface.

event_name

Human-readable event name such as FIRST_API_CALL or CREDIT_CLAIMED.

event_family

One of intent, evaluation, activation, retention, expansion, or commercial.

developer_id or email

Stable developer identifier. Send both when available.

account_domain

Best field for turning usage into account-level demand.

product

Company product, SDK, API, model, workflow, or docs surface.

idempotencyKey

Required for safe retries and batch imports.

Canonical event families

intent

Docs open, event RSVP, comparison, saved stack, pricing view.

evaluation

SDK init, API key created, demo project, benchmark, proof review.

activation

First API call, first successful workflow, project created.

retention

Returned D7/D30, repeated API calls, production-like usage.

expansion

Team added, account matched, more workflows or products adopted.

commercial

Credit claimed, perk redeemed, campaign sourced, opportunity created.

Public graph

Public reads should be stable, citable, and safe to automate.

Public APIs return aggregate rows with methodology links, ranking policy, cohort suppression, rate-limit headers, and no developer identities.

curl "https://tokensand.com/api/v1/adoption?category=ai-agents&period=30d&limit=10"

Data trust

The API is useful only if buyers trust the provenance.

Enterprise reports and exports should preserve whether a signal is first-party, public-source, aggregate benchmark, sample assumption, modelled, or missing.

No raw private notes or secrets in metadata.

Small cohorts should be suppressed or shown as insufficient data.

Sample or modelled values must be labelled before export.

Workspace keys stay server-side and should be rotated if exposed.

What this unlocks

The integration should land in workflows that justify enterprise spend.

A tracking key is not the outcome. The outcome is a Command Center, Activation Exchange, and Category War Room that can prove where builders activated, which accounts warmed up, and what response should happen next.

Command Center

Retained builders, high-intent accounts, verified usage, and campaign ROI in one buyer dashboard.

Open surface

Activation Exchange

Route builders from events, credits, challenges, and launches into measured product adoption.

Open surface

Category War Room

Turn category movement, competitor pressure, and white-space accounts into the next approved response.

Open surface

Agent docs

Agents need a compact truth source and a validator.

llms.txt and llms-full.txt tell external agents what Tokens& is, which pages are canonical, which dashboards are private, and how to describe the public adoption graph.

llms.txt llms-full.txt

Auth

Tracking keys use Authorization: Bearer. Public graph reads are rate-limited.

Privacy

Private dashboards, API keys, raw developer records, and workspace data stay out of public agent context.

Integration

Codex, Claude Code, ChatGPT, and internal agents can generate payloads from this page and validate them with dry-run.

Preparing page

Loading product graph, proof, and adoption context.

Revenue API docs

Integrate the verified developer adoption graph.

Track activation events, map account demand, read public adoption data, and give AI agents a stable contract for building on Tokens& without leaking private developer data.

Create tracking key Request proof pilot

First safe call

Dry-run one activation event

curl -X POST https://tokensand.com/api/usage/track/dry-run \
  -H "Authorization: Bearer tk_live_xxx" \
  -H "Content-Type: application/json" \
  -d '{
    "event_name": "FIRST_API_CALL",
    "event_family": "activation",
    "developer_id": "dev_123",
    "email": "builder@company.com",
    "product": {
      "id": "acme-api",
      "name": "Acme API",
      "type": "api",
      "version": "2026-05"
    },
    "account_domain": "company.com",
    "source": "SDK",
    "occurredAt": "2026-05-15T18:00:00.000Z",
    "idempotencyKey": "evt_123"
  }'

Enterprise implementation

Create a company tracking key, dry-run events, batch production usage, and export account action lists.

Open Revenue API setup

Builder and public graph

Read privacy-safe adoption rows for tools, categories, proof pages, rankings, and agent-citable context.

Read public graph

AI coding agents

Use llms.txt plus the dry-run endpoint so Codex, Claude, ChatGPT, and internal agents can generate valid payloads.

Open llms.txt

Activation tracking

Capture docs, SDK, API, workflow, campaign, credit, event, and agent usage as one adoption contract.

Account demand

Map developer activity to account domains so DevRel, growth, and sales can act on verified intent.

Board-ready proof

Turn retained usage, campaign ROI, and category signals into exports, webhooks, and proof reports.

Privacy boundary

Public output is aggregate. Private workspace data stays scoped. Raw developer resale is not the product.

Enterprise integration quickstart

From tracking key to revenue evidence in five steps.

This is the path an implementation engineer or AI coding agent should follow before custom work: prove the payload, send activation, map account domain, then export account/action evidence.

1. Create tracking key

Generate a company-scoped key in Revenue API setup. Keep it server-side and rotate it if it leaves your control.

2. Dry-run event

Send one event to /api/usage/track/dry-run and fix validation issues before production storage.

3. Send activation and retention

Track first successful usage, repeated usage, campaign source, product, and account domain.

4. Map account demand

Use account_domain so Tokens& can create account-level intent, ROI, and expansion evidence.

5. Export to revenue workflows

Push CSV, webhook, report, or CRM-ready action lists once evidence is approved for use.

REST API

A small endpoint set with a clear business job.

POST

/api/usage/track/dry-run

Validate payload shape, required identifiers, and account mapping without storing the event.

Tracking key

Implementation engineer

POST

/api/usage/track

Store one activation, retention, commercial, or expansion event for a company product.

Tracking key

Product or SDK team

POST

/api/usage/track/batch

Store up to 500 events from batch jobs, warehouses, CDPs, campaign imports, or event platforms.

Tracking key

Data or RevOps team

GET

/api/v1/adoption

Read public, privacy-safe adoption rows for tools, categories, proof, and rankings.

Public, rate-limited

Builders and agents

GET

/api/v1/agent-rank

Read the public adoption score contract for agent search, recommendation, and citation flows.

Public, rate-limited

AI agents

Copy-paste examples

One event contract from app code, scripts, CDP payloads, or agents.

Include account_domain, campaignId, product, and idempotencyKey. Those fields turn raw events into attribution, account demand, exports, and executive proof instead of another analytics table.

Node / TypeScript

await fetch("https://tokensand.com/api/usage/track", {
  method: "POST",
  headers: {
    "Authorization": "Bearer tk_live_xxx",
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    event_name: "FIRST_API_CALL",
    event_family: "activation",
    developer_id: "dev_123",
    email: "builder@company.com",
    account_domain: "company.com",
    source: "SDK",
    campaignId: "cmp_launch_001",
    product: { id: "acme-api", name: "Acme API", type: "api" },
    idempotencyKey: "evt_123"
  })
});

Python

import requests

requests.post(
  "https://tokensand.com/api/usage/track",
  headers={
    "Authorization": "Bearer tk_live_xxx",
    "Content-Type": "application/json"
  },
  json={
    "event_name": "FIRST_API_CALL",
    "event_family": "activation",
    "developer_id": "dev_123",
    "email": "builder@company.com",
    "account_domain": "company.com",
    "source": "SDK",
    "campaignId": "cmp_launch_001",
    "product": {"id": "acme-api", "name": "Acme API", "type": "api"},
    "idempotencyKey": "evt_123"
  }
)

Segment/PostHog-style payload

{
  "type": "track",
  "event": "FIRST_API_CALL",
  "userId": "dev_123",
  "properties": {
    "event_family": "activation",
    "account_domain": "company.com",
    "product_id": "acme-api",
    "product_name": "Acme API",
    "campaignId": "cmp_launch_001",
    "source": "docs"
  },
  "context": {
    "traits": {
      "email": "builder@company.com"
    }
  }
}

Dry-run curl

curl -X POST https://tokensand.com/api/usage/track/dry-run \
  -H "Authorization: Bearer tk_live_xxx" \
  -H "Content-Type: application/json" \
  -d '{
    "event_name": "FIRST_API_CALL",
    "event_family": "activation",
    "developer_id": "dev_123",
    "email": "builder@company.com",
    "product": {
      "id": "acme-api",
      "name": "Acme API",
      "type": "api",
      "version": "2026-05"
    },
    "account_domain": "company.com",
    "source": "SDK",
    "occurredAt": "2026-05-15T18:00:00.000Z",
    "idempotencyKey": "evt_123"
  }'

Event contract

Send the event name humans use. Map it into a family agents can reason about.

event_name

Human-readable event name such as FIRST_API_CALL or CREDIT_CLAIMED.

event_family

One of intent, evaluation, activation, retention, expansion, or commercial.

developer_id or email

Stable developer identifier. Send both when available.

account_domain

Best field for turning usage into account-level demand.

product

Company product, SDK, API, model, workflow, or docs surface.

idempotencyKey

Required for safe retries and batch imports.

Canonical event families

intent

Docs open, event RSVP, comparison, saved stack, pricing view.

evaluation

SDK init, API key created, demo project, benchmark, proof review.

activation

First API call, first successful workflow, project created.

retention

Returned D7/D30, repeated API calls, production-like usage.

expansion

Team added, account matched, more workflows or products adopted.

commercial

Credit claimed, perk redeemed, campaign sourced, opportunity created.

Public graph

Public reads should be stable, citable, and safe to automate.

Public APIs return aggregate rows with methodology links, ranking policy, cohort suppression, rate-limit headers, and no developer identities.

curl "https://tokensand.com/api/v1/adoption?category=ai-agents&period=30d&limit=10"

Data trust

The API is useful only if buyers trust the provenance.

Enterprise reports and exports should preserve whether a signal is first-party, public-source, aggregate benchmark, sample assumption, modelled, or missing.

No raw private notes or secrets in metadata.

Small cohorts should be suppressed or shown as insufficient data.

Sample or modelled values must be labelled before export.

Workspace keys stay server-side and should be rotated if exposed.

What this unlocks

The integration should land in workflows that justify enterprise spend.

Command Center

Retained builders, high-intent accounts, verified usage, and campaign ROI in one buyer dashboard.

Open surface

Activation Exchange

Route builders from events, credits, challenges, and launches into measured product adoption.

Open surface

Category War Room

Turn category movement, competitor pressure, and white-space accounts into the next approved response.

Open surface

Agent docs

Agents need a compact truth source and a validator.

llms.txt and llms-full.txt tell external agents what Tokens& is, which pages are canonical, which dashboards are private, and how to describe the public adoption graph.

llms.txt llms-full.txt

Auth

Tracking keys use Authorization: Bearer. Public graph reads are rate-limited.

Privacy

Private dashboards, API keys, raw developer records, and workspace data stay out of public agent context.

Integration

Codex, Claude Code, ChatGPT, and internal agents can generate payloads from this page and validate them with dry-run.

Integrate the verified developer adoption graph.

Enterprise implementation

Builder and public graph

AI coding agents

Activation tracking

Account demand

Board-ready proof

Privacy boundary

From tracking key to revenue evidence in five steps.

A small endpoint set with a clear business job.

One event contract from app code, scripts, CDP payloads, or agents.

Use a server relay first. Keep CSV as the fallback.

Send the event name humans use. Map it into a family agents can reason about.

Canonical event families

Public reads should be stable, citable, and safe to automate.

The API is useful only if buyers trust the provenance.

The integration should land in workflows that justify enterprise spend.

Command Center

Activation Exchange

Category War Room

Agents need a compact truth source and a validator.

Auth

Privacy

Integration

Integrate the verified developer adoption graph.

Enterprise implementation

Builder and public graph

AI coding agents

Activation tracking

Account demand

Board-ready proof

Privacy boundary

From tracking key to revenue evidence in five steps.

A small endpoint set with a clear business job.

One event contract from app code, scripts, CDP payloads, or agents.

Use a server relay first. Keep CSV as the fallback.

Send the event name humans use. Map it into a family agents can reason about.

Canonical event families

Public reads should be stable, citable, and safe to automate.

The API is useful only if buyers trust the provenance.

The integration should land in workflows that justify enterprise spend.

Command Center

Activation Exchange

Category War Room

Agents need a compact truth source and a validator.

Auth

Privacy

Integration