> For the complete documentation index, see [llms.txt](https://docs.socialhood.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.socialhood.app/social-app/invites.md).

# Invites

Socialhood is invite-gated. You need a valid code to sign up — and once you're in, you become a gateway for others.

## The rules

1. Every user gets **10 single-use codes per day** (UTC).
2. Codes **expire at day rollover** — yesterday's unused codes are dead. Fresh scarcity every day.
3. Redemption is transactional and race-safe: one code, one signup, exactly once.
4. Your invite graph is permanent — the app remembers who brought whom into the hood.

## Where to find your codes

The **Invites panel** lives in your Wallet view and in the right-hand column on desktop — `Your invites today · 7/10 left`, with copy-to-clipboard codes in monospace.

## Why invite?

Points. But deliberately anti-sybil: you earn invite points **only when your invitee activates** (their first key purchase), not on signup. Farming empty accounts earns nothing — bringing real users earns a lot. See [Points](/social-app/points.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.socialhood.app/social-app/invites.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.