Poppy Lab is an independent test bench for the Personal Agent Protocol, draft 0.3. Run a Personal Agent with your own model key, point it at two fictional Companies, and watch every step it takes: discovery, sign-in, signed Sessions, and changes that wait for your approval.
Bring an OpenAI or Anthropic key, or try the keyless protocol demo. The shops are fictional: nothing is charged or shipped.
“Move my delivery to Saturday.”
Poppy reads /.well-known/poppy.json, checks the Company's own sign-in server, and starts a Session signed with its own key.
The Company shows which agent is asking. Pick a fictional customer; access is read-only unless you also allow change proposals.
The agent proposes exact terms. The Company holds them until you approve in Poppy, then performs them at most once.
poppylab.dev/playground
A chat-first Personal Agent. Choose GPT-6 Luna or Sonnet 5 with your own key, connect a Company, and open the Inspector for the discovery document, the Session and every API call. Approval cards show exact terms; the model can't press them.
juniper.poppylab.dev
A neighbourhood grocery with a full customer account: basket, recurring delivery, orders, simulated invoices, profile and support cases. The website and your agent share the same data.
poppy:read poppy:write“Move my recurring delivery to Saturday.”
noodles.poppylab.dev
A noodle bar with a menu, delivery slots and scheduled orders. Change dishes or the slot; the approval shows the price difference first.
orders:read orders:write“Add a matcha ice cream and move it to Sunday lunchtime.”
Every visitor gets a separate copy of the fictional customers. An idle copy starts again after 24 hours.
Juniper and Lantern accept any Personal Agent with an HTTPS client_id that serves its metadata and keys, with redirect URIs from that metadata. Both speak Operations v2. Replace {company} with juniper.poppylab.dev or noodles.poppylab.dev.
| Code | What | Where, on https://{company} | Spec |
|---|---|---|---|
| DI | Discovery | /.well-known/poppy.json | §3 |
| RS | Protected resource | /.well-known/oauth-protected-resource | §3.2 |
| AS | Authorization server | /.well-known/oauth-authorization-server | §3.2 |
| ID | Your agent's identity | HTTPS client_id, metadata and JWKS | §4.1 |
| SI | Direct Sign-In | GET /oauth/authorize · PKCE S256 | §4.2 |
| TK | Tokens and refresh | POST /oauth/token · private_key_jwt, DPoP | §4.4–4.5 |
| RV | Revocation | POST /oauth/revoke | §4.6 |
| SH | Session header | Poppy-Session on every API request | §5.2–5.3 |
| AP | APIs | /openapi.json · OpenAPI 3.1 | §7 |
| EX | Excluded tasks | /poppy/excluded-tasks.json | §9.1 |
| OP | Approvals | 403 approval_required → resend with Poppy-Approval | Operations v2 |
Poppy's own identity: /agent/client.json and /agent/jwks.json.