Service twin · API + UI
Google Calendar
Test scheduling agents that create events, resolve conflicts, and coordinate attendees.
API + UIspec-groundedREST · MCP · CLI
Terminal
$ uv tool install blobfish-cli
$ blobfish twin login
$ blobfish twin-runs create --twins googlecalendar --ttl 60 --waitWhat’s inside
A deterministic, seeded, resettable replica: every operation below executes real state transitions against the twin’s own SQLite state — reads are hash-invariant, writes produce inspectable diffs, and reset restores the seed baseline.
Seeded entities
| Entity | Table | Fields | About |
|---|---|---|---|
| acl | acls | 6 | |
| acl_rule | acl_rules | 5 | |
| calendar | calendars | 11 | |
| calendar_list | calendar_lists | 6 | |
| calendar_list_entry | calendar_list_entries | 21 | |
| channel | channels | 10 | |
| color | colors | 5 | |
| event | events | 44 | |
| free_busy_request | free_busy_requests | 7 | |
| free_busy_response | free_busy_responses | 6 | |
| setting | settings | 4 |
Three surfaces, one state
Mount Google Calendar in a twin environment and the same seeded state serves vendor-shaped REST operations, an MCP endpoint for tool calling, and a generated bf-twin CLI — with copy-on-write sessions per rollout and a one-call reset to the seed baseline. Prefer raw HTTP? The same create works with curl:
API
$ curl -sS -X POST https://blobfish.ai/api/v1/twin/environments \
-H "X-API-Key: $BLOBFISH_API_KEY" -H "Content-Type: application/json" \
-d '{"services":["googlecalendar"],"ttl_minutes":60}'Known limitations
Spec-grounded surface with synthetic seeded values; operations outside the spec are not mounted.