Skip to main content
Every piece of data in Worktruck.app belongs to a tenant. Tenants are isolated at the database level — it is physically impossible for one tenant’s API request to return another tenant’s data.

​
How it works

  1. Your API key is tied to a tenant
  2. Every request sets a tenant context at the database level
  3. Database-enforced row filtering rejects any query that reaches for another tenant’s data
  4. Even a bug in our code cannot leak cross-tenant data

​
Tenant provisioning

Tenants are created automatically:
  • Stripe path: First subscription creates the tenant and returns an API key
  • x402 path: First payment from a new wallet creates the tenant
  • Keycloak OIDC path: First OAuth sign-in (dashboard session or Claude.ai custom connector) JIT-provisions a tenant keyed on the Keycloak sub claim. The mapping lives in the internal idp_users table — subsequent logins with the same sub resolve to the existing tenant

​
Plans

PlanDescription
freeAuto-assigned trial tier. Not a Stripe product — upgrade via Checkout.
proHigher limits. For individual developers and small teams.
scaleHighest limits. For production workloads.
enterpriseCustom limits. Contact us.

​
Tenant info

Retrieve your tenant details: 
GET /api/v1/tenant

{
  "id": "550e8400-e29b-41d4-a716-446655440000",
  "name": "My Company",
  "slug": "bks_a7f3k9m2p4x1",
  "plan": "pro",
  "created_at": "2026-04-01T00:00:00Z"
}
Sensitive fields (Stripe customer ID, metadata, active status) are not exposed through the API.