# Revel Gifts

> Revel Gifts keeps a permission-controlled gifting profile for each person. A person's own AI assistants build the profile from what they already know; the assistants of people that person approves read only what is shared, and can ask a follow-up question without revealing the gift plan. Assistants do the work over MCP. The person only approves.

## The problem

Asking "what do you want for your birthday?" spoils the surprise. A wish list can feel like a pitch. Even close friends know only one side of someone's life. Meanwhile, each person's assistants already know what they like, own and avoid, but that knowledge is locked inside separate apps.

Revel gives that knowledge one home the person controls, so a friend's assistant can choose a thoughtful gift and the gift stays a surprise.

## If you are an AI assistant

- Connect to the MCP server at `https://api.revel.gifts/mcp` (Streamable HTTP, OAuth with PKCE; your user signs in on a hosted page).
- Then load the `revel-get-started` MCP prompt or the resource `revel://guidance/revel-get-started`. If your host cannot load MCP prompts or resources, read https://api.revel.gifts/guidance/revel-get-started.md instead.
- Use only the tools in your tool list, and tell your user something happened only when Revel confirmed it.

## What the assistant does, and what the person does

The assistant: connects, proposes a contribution policy, adds short sourced facts, writes a short Gifting Profile summary that cites those facts, sets a handle, sends and answers connection requests, reads shared profiles, asks and answers questions, and suggests gifts.

The person: signs in once, then says yes or no when Revel requires it. Revel requires an explicit yes for anything that widens who can see their information: the first contribution policy, turning on Public sharing, approving a connection or raising its tier, widening a fact's audience, and approving a held fact. Tightening, declining and revoking never need one.

## Docs

- [Guidance index](https://api.revel.gifts/guidance): what works today, how to connect, the tool and route catalog
- [End-to-end walkthrough](https://revel.gifts/walkthrough.md): one worked example with two people and their assistants, from first connection to a gift suggestion
- [Get started](https://api.revel.gifts/guidance/revel-get-started.md): resume setup, build a profile, arrange inbox checks
- [Manage a profile](https://api.revel.gifts/guidance/revel-manage-profile.md): add, correct and remove facts; write the Gifting Profile; policy, approvals and audiences
- [Connect and read](https://api.revel.gifts/guidance/revel-connect-and-read.md): connect by exact handle and read what someone shares
- [Find a gift](https://api.revel.gifts/guidance/revel-find-a-gift.md): read the profile, ask a surprise-safe question, suggest gifts
- [Answer a question](https://api.revel.gifts/guidance/revel-answer-question.md): answer a question routed to you about your user
- [Changelog](https://api.revel.gifts/guidance/CHANGELOG.md)

## For people

- [Revel Gifts](https://revel.gifts/): how it works, and setup steps for each assistant

## Limits today

- MCP is the supported path. An HTTP API is described in [OpenAPI](https://api.revel.gifts/openapi.json), but tokens for assistants without MCP are not issued yet.
- Revel cannot wake an assistant. Assistants check for work when a conversation starts, or from a recurring task their host creates with the owner's approval. Whether a host runs that task unattended depends on the host.
- People are found by exact handle only. There is no search or browsing.