What format is a Pupul profile share in?

A signed JWT (ES256). The claims name the issuer, the scope, an expiry and a revocation id, and the display fields carry the readable profile subset the person chose to share. Anyone can verify the signature against the public JWKS at noctaracorp.com/.well-known/jwks.json without asking Pupul.

Can I verify a Pupul profile without trusting Pupul?

Yes. Check the public revocation list first, then verify the token signature against the published JWKS, then check the expiry and scope. All three artifacts are public files. Pupul's servers are out of the loop, and the full walkthrough is at pupulcorp.com/verify-a-pupul-profile.

What can an AI agent get from Pupul for free?

The MCP server at noctaracorp.com/api/mcp answers four tools with no auth: get_export_guide for 11 platforms, get_wait_times for the full export wait table, get_count_link for the free in-browser viewers, and get_pupul_facts for pricing and product facts. Same content as the public pages, as of 2026-08-27.

Do agents pay Pupul for user data?

No, and they never will. The paid lane sells verification and consented profile slices: an agent pays to check that a grant is real, current and unrevoked, or to read exactly the slice a person granted. Behavioral data is not for sale, to agents or anyone else.

Specification. Open. No account required to read or verify.

The Pupul profile: the open format and the agent surface

A Pupul profile belongs to the person it reads, and this page is the proof in the only form that counts: the share format, the verification path, and the agent tools are documented in the open, so everything important about a profile can be checked, moved, or revoked without asking Pupul for permission.

Written 2026-08-27. Everything on this page is live today; nothing here is a roadmap item unless it is labeled as one.

The principle

A format you can take elsewhere is the evidence you own it. A profile that can only be read inside the product that made it is not owned, it is rented. So the share format is plain, the keys are public, the revocation list is public, and the verification steps work with Pupul's servers out of the loop.

What a profile is made of

The source files The official data exports the platforms already owe you. They start on your device and, in the free Count, they stay there: the viewer runs in the browser tab and uploads nothing.
The Reading Pupul's interpretation of those files, rendered as one readable page. It is 6.99 a week or 69.99 a year, it belongs to you, and because it is an interpretation, you can mark any line of it wrong.
The share A signed, scoped, expiring grant of the profile subset you chose. This is the only part of a profile that ever travels, and it is the part this page specifies.

The share format, exactly

A share is a JWT signed with ES256. The signing keys are published as a standard JWKS. The claims that matter:

Claim	What it is
`iss`	Always `noctara`. Noctara is the engine that signs; Pupul is the product surface.
`scope`	`packet` for a profile share. A verifier must reject any other scope here.
`jti`	The grant id. This is what appears on the public revocation list when the person pulls the grant.
`exp`	Expiry. Shares are expiring by design; a share that cannot go stale cannot be safely granted.
display fields	The readable subset the person granted: `word`, `rhythm`, `force`, `posture`, `line`. Never the person's raw files, never their messages, never anything they did not scope in.

What is deliberately absent: there is no field for how a person folds under pressure, on this or any outbound surface. That line is documented in the privacy page and enforced in the build.

Verify a share without trusting Pupul

Check the revocation list first Fetch https://noctaracorp.com/.well-known/noctara-revocations.json. If the share's jti is on it, stop: the person said no, and that outranks a valid signature.
Fetch the public keys https://noctaracorp.com/.well-known/jwks.json. Standard JWKS, no account, no API key.
Verify the signature ES256, any JWT library. If it does not verify against the published keys, it is not a Pupul share.
Check exp, iss and scope Expired, wrong issuer, or a scope other than packet means reject.

Or let one endpoint do all four: GET https://noctaracorp.com/api/packet-public?token=... returns the granted display subset for a live share and a 401 for a missing, expired, or revoked one. The full independent walkthrough, with every artifact linked, is at how to verify a Pupul profile.

The agent surface, free today

Pupul runs an MCP server (Model Context Protocol, Streamable HTTP, stateless, JSON responses, no auth) at:

https://noctaracorp.com/api/mcp

Four tools, all read-only, all serving the same content as the public pages:

Tool	What it answers
`get_export_guide`	The exact steps to request a personal data export from any of 11 platforms, with the reported wait, download window and file contents. Same content as /data/tiktok and its ten siblings.
`get_wait_times`	The full export wait-times table for 11 platforms, every figure labeled reported or measured with its source. Same content as /data/wait-times, CC BY 4.0.
`get_count_link`	The free in-browser Count viewer for a platform. The file never leaves the person's device; the tool returns the link and says exactly that.
`get_pupul_facts`	What the Reading is, what it costs, what is free, and the privacy stance, stated the way the site states it.

Try it from a terminal:

curl -s https://noctaracorp.com/api/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
       "params":{"name":"get_export_guide",
                 "arguments":{"platform":"tiktok"}}}'

No tool on the free surface reads, stores, or can reach any user data. The server imports a static dataset generated from these pages and nothing else.

The paid lane for agents, stated honestly

Live today: verification. Checking a share is free at /api/packet-public, and the developer lane for acting on a person's behalf is ordinary OAuth, self-serve, documented at Pupul for developers: the first 1,000 reads a month are free, then 49 dollars a month for 25,000.

Roadmap, not live: machine-native payment for the same surface, so an agent can pay per verification or per consented profile slice without a human setting up an account first. The rails under evaluation are x402 and Stripe's Machine Payments Protocol. Neither is wired up today, and this page will say so plainly when one is.

Permanent, either way: agents pay for verification and for consented slices. Behavioral data is never the product. A person's files, messages, and history are not for sale at any price, to any buyer, on any rail.

Asked plainly

Why publish the format at all?

Because ownership claims are cheap and formats are checkable. If Pupul disappeared tomorrow, a person still holds their source files, their Reading, and this page describing exactly what their shares meant. That is what owning it means.

Can another company implement this?

They can verify everything: the format, keys, and revocation list are open so any verifier can be independent. The method underneath the Reading is patent pending (application 64/048,624), which covers how a profile is earned, not your right to hold, move, or revoke one.

Where do I report a gap between this page and reality?

support@pupulcorp.com. A spec that drifts from the running system is worse than no spec, so a mismatch is treated as a bug, not a docs chore.