How do I test a Cursor integration without a real team?

You do not need one. Point your client at a read-only Cursor replica that already holds the olympus-labs data set, and your code runs unchanged.

01 / The one change

Swap the base URL. Nothing else.

Your client talks to api.cursor.com. Point it at cursor.sandboxapis.dev instead: same paths, same JSON, same headers, same status codes. No team to create, no seed script.

For CI, use a pinned host. This page uses cursor-2026-08-g12.snap.sandboxapis.dev, the newest pin for Cursor, which answers the same bytes on every run, so an assertion written today still holds next month.

The live host, cursor.sandboxapis.dev, re-rolls daily and can carry a newer generation of the data set than cursor-2026-08-g12.snap.sandboxapis.dev; every answer on this page is for cursor-2026-08-g12.snap.sandboxapis.dev.

02 / Run it now

One request, no account.

request.sh

curl -u any-key: "https://cursor-2026-08-g12.snap.sandboxapis.dev/teams/members"

It answers with the members of the team, each with a name, an email at olympus-labs.dev and a role.

03 / Writes

A write gets Cursor's own error shape.

Every host is read-only. A write answers 403 with Cursor's own error body, naming what you tried, so your client's existing error handling meets a shape it knows.

403 · application/json; charset=utf-8

curl -s -X POST "https://cursor-2026-08-g12.snap.sandboxapis.dev/teams/members" -H 'content-type: application/json' -d '{"email":"test@olympus-labs.dev"}'

{"code":"error","message":"This universe is read-only. See what's covered at https://sandboxapis.dev/coverage. (You tried to POST /teams/members.) Tell us what you needed to write: https://sandboxapis.dev/feedback"}

04 / Where it stops

Coverage is counted, not claimed.

20 of 21 Cursor read surfaces are served and checked against a spec written from Cursor's own documentation and live captures, because Cursor publishes no machine-readable one. A call to one that is not covered returns a 404 with an X-SandboxAPIs-Coverage header, never invented data. The row-by-row list is on the Cursor reference and the coverage page.

Next: read the Cursor quickstart, or run the four-hop walk to watch one incident cross four services.

What this is not

Read this before you rely on it.

SandboxAPIs is read-only: a write returns the provider's own error unless your key has opted in to scratch writes, and those never reach anybody else. Coverage is bounded, and the manifest that says exactly where it stops is public. The data is a simulated company, not yours and not a copy of anybody's. And it reproduces what each vendor documents and publishes, not the vendor's undocumented behaviour, so keep one test against the real service for that.