-
Notifications
You must be signed in to change notification settings - Fork 0
API Access
orgware lets you reach the Tribal Record from your own tools — and from an AI assistant — with a personal API key. It's the same record you see in the library, returned as data, always within your ring.

Keys look like wcm_live_…. They're stored only as a hash, so the full key is
shown once when you create it — copy it immediately into a safe place (a
password manager). Lose it and you simply revoke it and make a new one.
A key carries your ring: a member's key sees cleared member/public records; a leader's key sees the whole corpus. Treat it like a password.
- Members can create, list, and revoke their own keys.
- Leadership has a dedicated API access page (waccamaw.org/members/api-access) for durable, non-expiring keys and ready-to-paste assistant configuration; an admin can also provision a key for another leader.
Send it as a bearer token:
curl https://members.waccamaw.org/api/query \
-H "Authorization: Bearer wcm_live_your_key_here"The record is exposed as a Model Context Protocol server at mcp.waccamaw.org.
Point any MCP-capable assistant (Claude, etc.) at it with your key and it can
search and cite the tribe's records for you, with the same ring rules and
source-backed verification.
-
claude.ai (web): when you create a key, the API access page shows a single
connector URL (
https://mcp.waccamaw.org/mcp?token=…). Paste it whole into claude.ai → Settings → Connectors → Add custom connector. The URL carries your key, so treat it like the key. -
Claude Desktop / Codex: use the
mcp-remoteconfig the page provides, with your key in anAuthorizationheader.
The assistant gets a small set of tools:
- whoami — confirm your identity and ring.
- search_corpus — search the records.
- list_records — browse by type.
- get_record — read a single record.
- get_source — open the primary-source scan behind a record.
Admins have a read-only SQL console (/api/query) for ad-hoc questions
against the roll — SELECT-only, single-statement, capped, with writes and schema
changes blocked. It's a safe way to answer "how many…" questions directly.
Revoke a key any time — on the API access page (leaders) or via the keys API (members). It stops working immediately; your other keys keep working.
Next: For leadership.
waccamaw.org · orgware
- Home
- What is orgware
- Getting Started
- The Tribal Record
- Meetings & Podcast
- API Access
- Contact & Directory
- For Leadership
- How orgware Is Built
- Maintaining This Guide
a product of hatcher.ltd