We made this API to make the community better for members. Connect Claude, Cursor, or any MCP client and put your agents to work.
Sign in with your AI Tinkerers account to create Agent API keys. Key access depends on your member, attendee, or organizer eligibility.
Sign in to create keysEverything below is reference: overview, ideas, quickstart, endpoints, limits, and the rules.
The AI Tinkerers Agent API lets eligible members, recent event attendees, city organizers, and their AI agents work with AI Tinkerers data programmatically: event discovery, chapter operations, RSVPs, message boards, sponsor context, jobs, public docs, and analytics, all within the same permissions available to the signed-in member on the website. Read the API Beta Terms.
Automate follow-ups, manage RSVPs, speaker pipelines, message boards, sponsor outreach, and chapter reporting.
Find upcoming events, RSVP, prepare demos, follow up with people you met, and stay connected to your chapter.
This is a community of AI builders. Wire the API into whatever you're hacking on and show us what happens.
Ideas that pay off fast. Each one works as a plain-English ask once your MCP client is connected.
"Which sponsors from our last three events haven't been thanked or re-engaged? Draft follow-ups."
"Thank yesterday's speakers, and list attendees who RSVP'd but didn't check in so I can nudge them."
"Who demoed something great in nearby chapters recently that we could invite to speak next month?"
"How is our RSVP and attendance trend versus last quarter? What changed?"
"Which upcoming events match my interests? RSVP me to the next one that fits my calendar."
"Who did I meet at last night's event? Draft a short follow-up to the two I talked demos with."
There are two ways to authenticate, and both grant exactly the same permissions:
sk_
prefix and are sent on every request as a bearer token. Keys inherit the member's website
permissions and can be scoped to read, write, generate, and export access.
Authorization: Bearer sk_YOUR_KEY
OAuth connections appear in your Agent API Keys list as "OAuth:
The fastest start is MCP. One command connects Claude Code to your chapter and community data — no API key needed, a browser window opens to sign in:
claude mcp add --transport http aitinkerers \
https://aitinkerers.org/api/agents/mcp/v1
Run /mcp inside Claude Code to complete sign-in, then ask: "Who has RSVP'd to my next AI Tinkerers event?"
Prefer a static key? Append
--header "Authorization: Bearer sk_YOUR_KEY"
to the command instead.
Settings → Connectors → Add custom connector, then paste the MCP URL and click Connect:
https://aitinkerers.org/api/agents/mcp/v1You'll be asked to sign in to AI Tinkerers and approve the scopes. That's it.
OAuth-capable clients can connect with just the URL. For clients that use static headers, add to your MCP config (mcp.json):
{
"mcpServers": {
"aitinkerers": {
"url": "https://aitinkerers.org/api/agents/mcp/v1",
"headers": { "Authorization": "Bearer sk_YOUR_KEY" }
}
}
}
curl https://aitinkerers.org/api/agents/v1/auth/validate \
-H "Authorization: Bearer sk_YOUR_KEY"
curl https://aitinkerers.org/api/agents/v1/meetups/search \
-H "Authorization: Bearer sk_YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{"query":"upcoming Seattle events"}'
Start with agents.md for when-to-use guidance, safety boundaries, and recommended agent behavior.
The live OpenAPI schema is public and generated from the deployed API surface.
The MCP endpoint exposes AI Tinkerers tools to compatible agent clients. Tool access is authenticated and scoped. OAuth 2.1 (authorization code + PKCE, with Dynamic Client Registration) and static bearer keys are both supported.
https://aitinkerers.org/api/agents/mcp/v1
Agent API responses include rate-limit headers such as
X-RateLimit-Limit
and
Retry-After
when throttled. Clients should use exponential backoff with jitter.
API errors are returned as structured JSON with HTTP status codes. Invalid paths return JSON guidance toward the correct
/api/agents/v1
namespace.
Agent API access is included for eligible AI Tinkerers members, recent attendees, and city organizers. There is no public paid API plan today.
Keep keys private, use the narrowest scopes possible, revoke unused keys, and never use Agent API keys for platform-internal operations.
Your agent is you: it acts with your permissions, transparently, in ways other members would expect. Take only the data you need. Community data stays in the community. Bigger ideas are welcome, surprises are not. Our Code of Conduct applies to API usage too. Read the full API Beta Terms.
Found a security issue or exposed key? Email [email protected]. Want to build something bigger than personal or chapter tooling? Tell us first at [email protected], we say yes a lot.