OrgHQ for AI agents
An AI assistant (ChatGPT, Claude, Gemini or any agent) can sign an association up for OrgHQ and move its website in for the person it works for, without the web forms. A human always proves the admin’s email with the code OrgHQ emails them, and always pays through the Stripe link.
The steps
- Start the signup: POST https://orghq.org/api/v1/signups (MCP tool start_signup) with the association’s name, the human admin’s email and name, and the country. OrgHQ emails a 6-digit code to that address.
- Ask your human for the code from the email (from “OrgHQ”, subject “Confirm your email for …”). Never guess it. Then POST /api/v1/signups/{signup_id}/confirm (confirm_signup). This returns the workspace token once: keep it secret and send it as “Authorization: Bearer <token>”.
- Payment is the human’s: GET /api/v1/checkout (get_checkout_link) returns a Stripe Checkout link. Give it to your human; they add a card or bank account there. The API never takes card details. The workspace opens once the method is saved (poll GET /api/v1/workspace).
- Move the website: POST /api/v1/website-import (start_website_import) with the current site’s address, then poll GET /api/v1/website-import (get_website_import). Pages, events and news arrive as drafts; nothing is published or emailed.
- Members: POST /api/v1/members/import (import_members) with the member export as CSV (try dry_run first). You get counts and row numbers back, never anyone’s details.
- Show your human the drafts in the admin, and when they agree, POST /api/v1/drafts/publish (publish_drafts).
- Optional: GET /api/v1/checkout?move=white-glove gives the link for the White-Glove Move ($500 one time; $250 for a founding association, decided by OrgHQ and given back as amount_cents), where OrgHQ finishes the move with your human in a one-hour video session.
If you get stuck
If you get stuck or something looks wrong, call report_problem (or POST /api/v1/support) with what you tried and the request_id; then tell your human that the OrgHQ team has been told. Never include the email code or the API token.
Endpoints
JSON over HTTPS on https://orghq.org. The machine-readable list is /api/v1/openapi.json (OpenAPI 3.1). Every error answers {"error": {"code", "message", "request_id", "support"}} with a stable code.
| Call | MCP tool | Token | What it does |
|---|---|---|---|
GET /api/v1/slug-availability | check_slug | none | Check a web address. Is <slug>.orghq.org free for a new workspace? The same rules as the signup form. |
POST /api/v1/signups | start_signup | none | Start an association’s signup. Makes the workspace (waiting) and emails a 6-digit code to admin_email. Ask your human for the code, then call confirm_signup. Never guess the code. Same rules and limits as the orghq.org signup form. |
POST /api/v1/signups/{signup_id}/resend | resend_signup_code | none | Send a new email code. Emails a fresh 6-digit code to the signup’s address; the old one stops working. |
POST /api/v1/signups/{signup_id}/confirm | confirm_signup | none | Confirm with the emailed code. The 6-digit code your human read in the email from OrgHQ. Returns the workspace token ONCE: keep it secret, never show it in a chat transcript, never send it to report_problem. |
GET /api/v1/workspace | get_workspace | required | The workspace, its plan and its setup checklist. Name, addresses, plan and trial state, whether it still waits for its payment method, the setup checklist and the import’s state. |
GET /api/v1/checkout | get_checkout_link | required | A Stripe Checkout link for the human. The plan’s payment step (a card or bank account; nothing charged during the trial) or, with move=white-glove, the White-Glove Move ($500; $250 for a founding association, decided by OrgHQ: the answer gives amount_cents). Give the link to your human: the API never takes card details. |
POST /api/v1/website-import | start_website_import | required | Move the current website in, as drafts. Reads the association’s public website (its home page, navigation and sitemap; robots.txt honoured) and writes pages, events and news as DRAFTS. Nothing is published or emailed. Poll get_website_import. |
GET /api/v1/website-import | get_website_import | required | The import’s progress and report. queued, running, done or failed; what was read, what was drafted, and the problems. |
POST /api/v1/members/import | import_members | required | Load the member list (CSV). The People import’s own rules: an email column is required; exports from Wild Apricot, Join It, MemberClicks and Glue Up are recognized; up to 2 MB and 5,000 rows. Board Member tags are not applied. Answers counts and row numbers only. Over REST send the CSV as the body (text/csv) or as JSON {csv}. |
POST /api/v1/drafts/publish | publish_drafts | required | Publish what the import drafted. Publishes the import’s drafts of the kinds asked (default all). Only after your human has looked them over. Events offering CE, scheduled events and anything changed since the import stay drafts. Nobody is emailed. |
POST /api/v1/support | report_problem | optional | Tell the OrgHQ team you are stuck. If you get stuck or something looks wrong, report it with what you tried and the request_id; then tell your human the OrgHQ team has been told. Never include the email code or the API token. A workspace token is optional (it names the workspace). |
MCP
The same operations are tools on a remote MCP server at https://orghq.org/mcp (streamable HTTP, JSON responses, no session). The signup tools need no token; the others take the workspace token in the Authorization header. For a client that reads a JSON configuration:
{
"mcpServers": {
"orghq": {
"type": "http",
"url": "https://orghq.org/mcp",
"headers": {
"Authorization": "Bearer orghq_…"
}
}
}
}
The rules
- The workspace token is shown once and stored only as a hash. An admin can also create a key under Settings → Your Data → AI agent access, for an agent working in a workspace that already exists: it is shown once too, acts as that admin, and takes the place of the signup steps (up to 10 live keys per workspace).
- An admin can revoke any token under Settings → Your Data → AI agent access; a token also stops when the admin it acts as is removed or blocked, or the workspace closes.
- The API never takes card or bank details. Checkout links are for the human to open.
- Imports write drafts; publishing is its own call, made after the human has looked.
- Member imports answer with counts and row numbers only, and never grant admin access (Board Member tags are not applied).
- Limits: three signups an hour from one connection and three a day for one email address; code guesses, imports and reports are limited too. A limit answers 429 with retry_after_seconds.