> ## Documentation Index
> Fetch the complete documentation index at: https://docs.proofage.net/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP examples

> Prompts that work well with the ProofAge MCP server, from integration to support.

Plain requests work; the assistant picks the tools. These map directly onto them.

## Integrate

> Integrate ProofAge age verification into this app. Use a test workspace, the Browser SDK on the checkout page, and a webhook handler that marks the user as verified.

The assistant creates a test workspace, reads its keys and the docs, writes the code, and asks you to complete one verification with your camera. The full, reusable version is the [integration prompt](/integration/integration-prompt).

> My webhook handler returns 401 for ProofAge webhooks. Fetch the last delivery for verification 550e8400-… and replay it against [http://localhost:3000/webhooks/proofage](http://localhost:3000/webhooks/proofage).

Uses `list-webhook-deliveries` and `get-webhook-delivery-request`, which returns the exact signed request to send with curl.

## Investigate

> Why was verification 550e8400-… declined?

Reads the decision, its reason, and what the person submitted.

> What was our approval rate last month, by workspace?

Uses `get-verification-stats`, which answers with the same numbers as the console's Dashboard: live workspaces only, so test traffic is left out. For your own reporting, count the [webhooks](/integration/webhooks) you receive, or read verifications with the [API reference](/api-reference/overview).

> Did anyone verify under user\_12345 more than once this week?

Uses `list-verifications` filtered by `external_id`.

## Support

> Send a verification link for customer 8812 in the "Checkout" workspace and give me the URL.

Uses `create-verification` and returns the link to send.

> Block the face from verification 550e8400-… — the selfie was a photo of a screen.

Prepares the block, shows you what will happen, and confirms with the reason `presentation_attack` once you agree.

> The person behind verification 550e8400-… asked us to delete their data. Erase it.

Prepares the erasure, shows what will be removed and what stays, and confirms with the reason `data_subject_request` after you agree. Erasure cannot be undone.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.