Kinetic for developers

Pricing research your agent can run.

Connect through REST or MCP to create studies, manage their lifecycle, monitor fieldwork, and work from deterministic results.

Choose a connection

REST API

Base URL

https://api.kineticpricing.com/v1

The REST API fits hosted integrations, backend services, and HTTP-based agent platforms. Plain JSON over HTTPS, stable error envelopes, and explicit idempotency on writes.

It accepts OAuth access tokens and scoped Kinetic API access tokens, so it serves both user-authorized clients and installed integrations.

MCP

Endpoint

https://mcp.kineticpricing.com/mcp

Built for MCP-capable agent hosts.

Uses OAuth and current MCP protocol negotiation, and exposes capability discovery, schemas, annotations, tasks, and URL interactions.

Static kp_live_ tokens do not work on MCP.

Platform adapters

Platforms that store a fixed secret at install time connect through the REST API with a scoped Kinetic API access token.

Authentication

Three credential paths cover every integration shape. All three resolve to the same capability registry with the same enforcement.

01

OAuth with PKCE

A person authorizes your client through the standard Authorization Code flow with PKCE. The agent then acts for that signed-in user, within the scopes the user approved.

02

Service accounts

Approved Workspace automation authenticates with client credentials bound to one workspace. Workspace owners create and rotate these from the workspace surface.

03

Kinetic API access tokens

REST integrations that hold a fixed secret use a scoped kp_live_ token. Any signed-in user creates one in Integrations, bounded by the authority their current role holds. Create a token in Integrations

  • You can grant only authority you currently hold.
  • Kinetic reevaluates role, plan, tenant, account state, and entitlements on every request.
  • Tokens never unlock paid features.
  • Raw access tokens appear exactly once. Put them straight into your integration's secret store.

What agents can do

One registry defines all 100 capabilities. The REST router, the OpenAPI document, the MCP tool list, and this page read the same source, so they always agree.

Results come from deterministic calculations on your respondents' answers: same inputs, same result, every time.

Account setup and onboarding

5 capabilities

kinetic.account_get kinetic.help kinetic.signup_complete kinetic.signup_start

Study recommendation, creation, launch, and lifecycle

23 capabilities

kinetic.method_list kinetic.method_recommend kinetic.respondent_link_get kinetic.study_archive

Progress, fieldwork quality, results, and exports

11 capabilities

kinetic.evidence_get kinetic.narrative_generate kinetic.narrative_get kinetic.results_export_csv

Teardowns and research records

7 capabilities

kinetic.research_download kinetic.research_get kinetic.research_list kinetic.teardown_create

Workspace planning, scenarios, decisions, and outcomes

36 capabilities

kinetic.cohort_archive kinetic.cohort_create kinetic.cohort_link_create kinetic.cohort_list

Billing handoffs and account settings

18 capabilities

kinetic.api_token_create kinetic.api_token_list kinetic.api_token_revoke kinetic.api_token_rotate

No capability creates, edits, imports, or simulates respondent evidence. Agents work from fieldwork; they never manufacture it.

Permission and safety model

User-bound identity

Every credential maps to one user in one tenant. Requests for another tenant's records return nothing, not an error you can probe.

Narrow scopes

Grants are explicit and role-bounded. Full access (kinetic.full) stays reserved for the account owner.

Live enforcement

Role, plan, and account state apply at request time, not at token creation. A downgraded role narrows a token immediately.

Risk annotations and idempotency

Every capability carries machine-readable risk annotations. Writes accept idempotency keys, so a retried request cannot double a side effect.

Payment stays human

Purchases hand off to Stripe-hosted checkout that the account holder completes. Agents never enter card details and never spend without a person.

Revocation, expiry, and audit

Tokens expire on schedule, revoke immediately, and leave audit records. Rate limits apply per credential.

Respondent evidence is off limits

No API surface creates, edits, imports, or simulates respondent answers. Evidence enters Kinetic only through real fieldwork.