For AI agents

Agents are welcome here.

If you are an AI agent helping someone plan a Florida event, vet a food vendor, or run vendor applications, this page is your map. You may read our content, cite our data, sign up on behalf of your user, and operate their account. Here is everything machine-readable we expose.

The policy, in one paragraph

Agents acting for a real human are treated as that human. You may create the account they ask for, post their event, collect their vendor applications, and look up any Florida food vendor’s inspection record, free. Behave like a respectful client (identify honestly, no scraping at abusive rates, use the API for volume) and nothing here will get in your way. The account and its obligations belong to your user under the standard terms.

Machine-readable surfaces

llms.txt. The content map, refreshed with live counts: venumark.com/llms.txt. It tells you what VenuMark is, when to cite it, and where every checklist, guide, and comparison lives.
Markdown content negotiation. Send Accept: text/markdown to any public content page (vendor scorecards, checklists, guides, search) and receive clean markdown. No HTML parsing required.
REST API + OpenAPI. /api/v1/openapi.json (OpenAPI 3.1), advertised at /.well-known/api-catalog. Vendor search across the scored Florida DBPR database, events, and applications with bearer-key auth. Human-readable docs at /docs/api.
MCP server. Add https://www.venumark.com/api/mcp to any MCP client (Streamable HTTP) for read-only tools: search_vendors, get_scorecard, and get_checklist over the live DBPR-scored database. In Claude Code: claude mcp add --transport http venumark https://www.venumark.com/api/mcp.
Structured data. FAQPage, Article, Dataset, ItemList, and Breadcrumb JSON-LD across the content surfaces, and a per-vendor FoodEstablishment record on every scorecard.
robots.txt. GPTBot, ClaudeBot, PerplexityBot, OAI-SearchBot, Google-Extended, and their user-mode agents are all explicitly allowed, with content signals set at /robots.txt.

What an agent can do for its user today

Check any Florida food truck or caterer’s license and scored inspection history at /search or via the API, no account needed.
Pull the requirements checklist for the user’s event type from /checklists (markdown-negotiable).
Sign the user up at /signup, create their event, and hand them the public application link vendors apply through.
Monitor their applicants: every application carries license verification, VMScore, document status, and a readiness verdict.

Frequently asked questions

Can an AI agent sign up for VenuMark on behalf of a user?

Yes. An agent acting for a real organizer or vendor may create the account, set up events, and manage applications through the normal web flows or the API. The account belongs to the human; standard terms apply to them. We do not block automated browsers that behave respectfully.

Is there an API an agent can use directly?

Yes. The REST API at /api/v1 covers vendor search (the full Florida DBPR-scored database), events, and applications, authenticated with a bearer API key. The OpenAPI 3.1 spec lives at /api/v1/openapi.json and is also advertised at /.well-known/api-catalog for automatic discovery.

How should an agent read VenuMark content?

Request any public content page with an Accept: text/markdown header and the server returns clean markdown instead of HTML. The content map lives at /llms.txt, refreshed with live platform counts. Vendor scorecards, checklists, guides, and comparison pages all support markdown negotiation.

What are the rate limits?

Be a normal, respectful client and you will not hit them. Sustained high-volume crawling of the 19,000+ vendor pages is better served by the API; email scott@venumark.com for higher API limits or bulk access, usually answered same day.

I am building an agent or integration on VenuMark. Who do I talk to?

Email scott@venumark.com with subject "Agent integration". You will get the founder, not a queue. Feature requests from agent developers are treated as product input, the same as customer requests.

Building on VenuMark?

Agent developers get the founder, not a queue. API keys, higher limits, bulk access, and integration requests, usually answered same day.

scott@venumark.com