Public developer documentation, OpenAPI, MCP, and authenticated API keys for AI Tinkerers agents.
The AI Tinkerers Agent API lets eligible members, recent event attendees, city organizers, and their AI agents work with AI Tinkerers data programmatically. Use it for event discovery, chapter operations, RSVPs, message boards, sponsor context, jobs, public docs, and analytics within the same permissions available to the signed-in member on the website.
Find upcoming events, summarize event details, prepare demos, and retrieve public community resources.
Manage chapter context, RSVPs, speaker pipelines, message boards, sponsors, and follow-up workflows.
Connect Claude, Cursor, Codex, scripts, and MCP clients to permissioned community data and actions.
Agent API keys use the
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
Validate a key before calling other endpoints:
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"}'
curl https://aitinkerers.org/api/agents/v1/weblogs/search \
-H "Authorization: Bearer sk_YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{"query":"chapters near Vancouver"}'
Configure your MCP client with
https://aitinkerers.org/api/agents/mcp/v1
and pass the same Agent API key as a bearer token.
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.
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.
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 keys