Stripe API

Stripe records

The examples below are seed record fragments. Put them inside a complete seed with matching referenced records before validating or importing it.

Stripe seed records use explicit prefixed IDs: cus_, prod_, price_, in_, ch_ and sub_. References must point to records in the same seed.

Amounts are integer cents. Where supported, created_offset is a nonnegative number of seconds before the epoch; a larger value means an older record.

"recurring": { "interval": "month", "interval_count": 1 }

{
  "id": "in_example",
  "customer": "cus_example",
  "status": "paid",
  "currency": "usd",
  "lines": [
    { "description": "Monthly plan", "amount": 4000, "quantity": 1 }
  ],
  "charges": [
    { "id": "ch_example", "amount": 4000 }
  ]
}

{
  "id": "sub_example",
  "customer": "cus_example",
  "price": "price_monthly",
  "quantity": 1,
  "current_period_start": 1766361600,
  "current_period_end": 1769040000,
  "cancel_at_period_end": false
}

Seed file structure

This is a valid empty starting world:

{
  "name": "my-seed",
  "version": 1,
  "epoch": 1767225600,
  "clock_mode": "manual",
  "data": {}
}

With a manual clock, time moves through worlds clock advance or the admin API. Auto mode also advances by auto_tick_seconds on eligible API requests. Authentication, injected failures and preflight refusals do not tick; see logical clock behavior.

Loading a seed emits no events or webhooks. The world records the parsed seed's canonical-JSON SHA-256 as seed_hash; generated record IDs derive from that hash and world counters. See determinism.

Import a Stripe account

Provide a restricted read-only key through STRIPE_API_KEY, then run:

worlds seed import --from-stripe --name my-account --manifest worlds/my-account.manifest.json

The importer reads supported account records and writes a validated seed. By default it samples up to 100 objects per resource and writes seeds/my-account.json, or the directory set by WORLDS_SEEDS_DIR.

This is pseudonymization, not anonymity. Amounts and timing can still identify an account. Product and price IDs remain verbatim, including merchant-chosen text. Review the manifest before sharing an imported seed.

The same source state and options produce identical files. The default epoch comes from the newest source creation timestamp, rounded up to UTC midnight.

Referential integrity

Validation rejects unknown fields, duplicate IDs, missing references and inconsistent history. Errors name the JSON path to fix.

For Stripe, it also rejects charges on unpaid invoices, over-refunded charges, subscriptions on one-time prices and inverted periods.

Validate the complete seed before use:

worlds seed validate my-seed.json

Save a world's current state as a seed

In the dashboard, choose Save as starting setup from an eligible world. From the CLI:

worlds world export w_abc123def456 --name my-fork

The admin equivalent is GET /admin/worlds/:id/export-seed?name=my-fork. Use the result to start another test from the state your agent produced.

The export uses the world's current logical clock as its epoch and validates as a seed. Its lossy report lists state the seed format cannot retain:

Stripe and legacy record offsets remain relative to the new epoch.

Exporting and reloading represents settled state, not a replay of the run. Re-exporting that loaded world preserves the same data block.

Library seeds

Bundled seeds are synthetic fixtures. See the generated seed catalog for their builders and starter packs for ready-made tasks.