Skip to content
ContentRemovalDeskDocumentation

Operate & monitor

Usage & plan capacity

Measure active API protection time and the creator activations and technical capacity shared with your agency.

REST API · JSONv0.8.0 · Live CRD integration
On this page

One agency bill

The public offer is €69 per active creator per month for 1–9; €59 each for all active creators from 10 with one seven-day agency trial. Adding a creator is free; explicit activation starts billing. The portal and API share the same paid activation. Aliases, official profile URLs, API access and signed webhooks are not separate charges.

Existing package and negotiated agreements retain their terms. Usage in UTC creator-months is informational; it does not reproduce Stripe billing periods, trial allowances, taxes, invoice credits or proration calculations. Use agency invoices as the financial record.

Read a monthly estimate

GET /v1/usage?month=YYYY-MM requires usage:read. Omit month for the current UTC month. The result includes creator_seconds, creator_months, active_creator_count and measured_through.

active_creator_count counts creators contributing positive time during the measured period, not everyone currently enrolled. This is informational, not an invoice: there is nothing to pay separately for API usage. The live billing_basis is active_api_scan_schedule.

Manage protection

Open /agency/billing to activate or pause creators and review invoices. Use /agency/api for keys and signed webhook delivery.

For active_creators, capacity describes a technical roster limit, not purchased seats. Existing agreements retain their billing and capacity until the owner switches in /agency/billing after the previous subscription ends. Package purchases and upgrades are retired. The previous signed agreement stays in history; the new agreement must be signed before activation. Creating extra API keys does not increase limits.

Shared entitlement, separate usage metrics

Recurring work is scheduled by CRD. For active_creators, the explicit protection PUT updates the same billable activation as the portal. For legacy agreements it controls only API dispatch. Neither usage metrics nor an accepted HTTP request prove a payment succeeded.

Request & response example

GET/v1/usage
curl --request GET 'https://api.crd.systems/v1/usage?month=2026-09' \
  --header "Authorization: Bearer $CRD_API_KEY"
Use your secret key in the environment variable.
Example response · 200
{
  "month": "2026-09",
  "period_start": "2026-09-01T00:00:00.000Z",
  "period_end": "2026-10-01T00:00:00.000Z",
  "measured_through": "2026-09-16T00:00:00.000Z",
  "active_creator_count": 1,
  "creator_seconds": 1296000,
  "creator_months": 0.5,
  "estimated_subtotal_cents": null,
  "minimum_monthly_cents": null,
  "estimated_total_cents": null,
  "currency": "EUR",
  "estimate": true,
  "simulated": false,
  "scope": "agency",
  "billing_basis": "active_api_scan_schedule"
}

Illustrative response. Replace example resource IDs with the IDs returned by your API requests. View endpoint details.