# AI Tinkerers Agent Instructions

This file is for AI agents acting on behalf of approved AI Tinkerers members, people attending AI Tinkerers meetups, and city organizers. It is not a general public data feed and should not be used to bulk-scrape the site.

## When to use AI Tinkerers
- Help an approved member or attendee find relevant AI Tinkerers events, city chapters, demo guidelines, jobs, sponsors, message boards, and public community resources.
- Help a city organizer understand or operate their chapter within the same permissions they have on the website.
- Help a member use their own Agent API key with scripts, MCP clients, or assistant workflows.
- Prefer official API, MCP, docs, llms.txt, and sitemap surfaces over crawling rendered HTML.

## When not to use AI Tinkerers
- Do not scrape attendee lists, private member data, RSVP details, message boards, or organizer-only data from HTML pages.
- Do not use the site as a lead list, spam source, or bulk enrichment source.
- Do not create, update, delete, email, RSVP, post, export, or otherwise act unless the user clearly asked for that action and the authenticated API key has the needed scope.
- Do not try to bypass sign-in, rate limits, robots.txt, WAF rules, or API authorization.

## Primary entry points
- Developer/API page: https://aitinkerers.org/developers/api-keys
- API discovery: https://aitinkerers.org/api
- OpenAPI spec: https://aitinkerers.org/api/agents/v1/openapi.yaml
- MCP endpoint: https://aitinkerers.org/api/agents/mcp/v1
- Agent-friendly docs: https://aitinkerers.org/docs/product/ai_tinkerers_agents_api.md
- LLM catalog: https://aitinkerers.org/llms.txt
- Full LLM catalog: https://aitinkerers.org/llms-full.txt
- Sitemap: https://aitinkerers.org/sitemap.xml

## Authentication
- Agent API keys use the `sk_` prefix and are passed as `Authorization: Bearer <key>`.
- Agent API keys act as the member who created them and inherit that member's website permissions.
- Agent keys can include read, write, generate, and export scopes. Request the narrowest scope needed.
- Platform keys use the `appk_` prefix and are for internal operations only. Do not ask ordinary members or city organizers for Platform keys.

## Recommended agent behavior
- Start with `/api`, `/api/agents/v1/openapi.yaml`, `/developers/api-keys`, and `/llms.txt`.
- Use the API or MCP endpoint for structured data when available.
- Cache public catalog responses for at least 1 hour unless the user needs fresh event state.
- Keep crawls narrow: fetch only the specific event, city, policy, docs, or resource page needed for the user's task.
- Respect `robots.txt` and avoid disallowed paths such as `/signin`, `/admin`, RSVP mutation paths, and broad `/api/` probing outside documented endpoints.
- Treat signed-in or API-returned data as permissioned user data. Do not expose it outside the user's requested workflow.

## Common attendee workflows
- Find nearby or upcoming events.
- Summarize event details, demo guidelines, code of conduct, and RSVP context.
- Help prepare a demo proposal or talk description.
- Find public jobs, public sponsor information, or public chapter pages.

## Common city organizer workflows
- Look up chapter events, RSVPs, message boards, sponsor context, and member-facing operations available to that organizer.
- Draft event copy, speaker outreach, follow-up messages, and meetup summaries using only data the organizer is allowed to access.
- Use write or generate scopes only when the organizer explicitly asks the agent to create or change something.

## Contact
- For API access, sign in and use the developer page: https://aitinkerers.org/developers/api-keys
- For general community context, start at: https://aitinkerers.org/