Skip to content

About

Is your site ready for AI agents? Test it against Poppy (the Personal Agent Protocol): 111 checks for poppy.json, OAuth & DPoP, sign-in and operations. npx allowfy-check

Topics

Resources

Stars

2 stars

Watchers

0 watching

Forks

Latest commit

 

History

3 Commits

Folders and files

Repository files navigation

Allowfy Check: the Poppy conformance tester

Is your site ready for AI agents? Test any domain against Poppy, the Personal Agent Protocol, in one command.

npm license checks

npx allowfy-check check https://your-domain.com

Customers are starting to send AI assistants to book, buy and change orders for them. Poppy is the open protocol for how those agents do it:

  • they find a business through /.well-known/poppy.json;
  • they prove who they are with signed assertions;
  • they hold DPoP-bound tokens;
  • they sign customers in;
  • they propose changes that customers approve.

Allowfy Check tells you, requirement by requirement, what your implementation gets right and what it doesn't. It shows exactly what was sent, what came back, and the line of the spec it's held to.

No terminal? Run the first 20 checks in your browser at check.allowfy.com.

What it checks

111 checks: all of the official validator's, plus 37 for the parts it doesn't cover yet.

Milestone Checks Covers
1. Foundation 42 poppy.json discovery, OAuth server metadata, Sessions, DPoP (replay, key binding, ath, nonces)
2. Interfaces 32 OpenAPI, MCP servers (Bearer and DPoP), conversations
3. Sign-in and accounts 17 Device Sign-In, Account Tokens, sign-out: invalid_scope, account_mismatch, narrower scopes only, immediate sign-out
4. Operations extension 20 Propose, confirm, cancel: exact-revision approval, terms_changed, at most once, ownership by account, Retry-After

Milestones 3 and 4 come from this project. Every check quotes the requirement it tests, word for word, and links to it.

What you see

✗ discovery.https  poppy.json is served over HTTPS at the well-known path      spec 3
  Requirement:  "A Company MUST publish its poppy.json document at
                 https://{domain}/.well-known/poppy.json over HTTPS"
  Sent:         GET https://example.com/.well-known/poppy.json
  Got:          404 Not Found
  Expected:     200 with the poppy.json document
  Likely cause: Nothing is published at https://example.com/.well-known/poppy.json.
                Some frameworks and static hosts skip dot-directories like
                .well-known unless configured to serve them.
✓ discovery.redirects-https  Every redirect of the well-known URL is to an HTTPS URL
- discovery.json  poppy.json is a JSON object
  poppy.json couldn't be loaded (see discovery.https).

Deeper checks: Sessions, sign-in and operations

These need a test Personal Agent: a key pair, plus two small files you host anywhere over HTTPS.

npx allowfy-check keygen --base-url https://staging.example.com/poppy-test
# host .poppy/agent.json and .poppy/jwks.json at the URLs it prints, then:
npx allowfy-check check https://staging.example.com \
  --probe https://api.staging.example.com/me \
  --propose 'POST https://api.staging.example.com/orders/ord_1/exchanges {"item_id":"itm_1"}'
  • Sign-in. The tool shows you the sign-in link and code, and you approve in a browser.
    • --decline also asks you to decline one sign-in.
    • --other-account asks you to use a second test account.
  • Proposing is safe. --propose only proposes and cancels, so nothing is performed.
  • --execute also confirms one proposal, so your system performs it. Use it in a test environment only.
  • Agents without the extension. --plain-identity <dir> adds a second agent whose agent.json doesn't list the operations extension, to check it gets no operations.
  • --json prints machine-readable results.

In CI

The exit code is 1 when a MUST check fails, so conformance can't silently break:

# .github/workflows/poppy.yml
name: Poppy conformance
on: [push, pull_request]
jobs:
  poppy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/setup-node@v4
        with: { node-version: 22 }
      - run: npx allowfy-check@latest check https://staging.example.com --milestone interfaces

How it relates to the official validator

The Poppy project publishes an official company validator. It covers milestones 1 and 2, and says that sign-in and extensions aren't checked yet. Allowfy Check:

  • runs that validator unmodified (vendored under vendor/, Apache 2.0);
  • adds the sign-in, account and operations checks in the same style, with the same result format.

It's independent: not affiliated with the protocol's authors. Where a result looks wrong, each failure links to the spec's feedback form.

Develop

npm install
npm test          # every quote in the catalog appears word for word in reference/
npm run build     # bundles dist/allowfy-check.mjs
node src/index.ts check https://example.com

Node 22.18 or later runs the TypeScript sources directly. The checks live in src/:

  • catalog.ts: ids, levels and quotes;
  • sign-in.ts;
  • operations.ts.

Issues and pull requests are welcome.


Made by Allowfy, the door between AI agents and your business: your rules decide what agents may do, customers approve, risky actions wait for your team, and every step is on a signed record. Allowfy passes every check that applies to it.

About

Is your site ready for AI agents? Test it against Poppy (the Personal Agent Protocol): 111 checks for poppy.json, OAuth & DPoP, sign-in and operations. npx allowfy-check

Topics

Resources

Stars

2 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages