# Food Web API

> One REST API for the local food network — kitchens, farms, bookings, payments, credits, and referrals, reachable through a single predictable interface. JSON in, JSON out.

The Food Web API developer portal (api.foodweb.network) documents and surfaces the **Platform API** — a REST interface hosted on Firebase Cloud Functions at `api.foodweb.network/v1`. This portal is a static Next.js site for developers; the API runtime itself is separate. Authentication uses Firebase ID tokens sent as `Authorization: Bearer` headers. Eight API domains cover map discovery (public), bookings, payments, credits, referrals, messaging, suggestions, and moderation reads. Platform-admin routes (finance, credits ops, partner controls) are omitted from the public reference. The portal includes a getting-started guide, interactive OpenAPI endpoint reference, and a developer dashboard for API keys and token management. Current API version: 0.3.0.

Food Web also runs a remote **MCP server** (Model Context Protocol) at `https://mcp.foodweb.network` — Streamable HTTP, stateless JSON. AI agents (Claude, Cursor, and any MCP client) get 25 typed tools: 18 for the food asset map (anonymous search + role-gated curation) and 7 for the community forum (visibility-filtered reads; authenticated posting/voting as the key's account). Auth is a free portal-issued `fw_` API key or a Firebase ID token; anonymous callers get public reads. Every mutating tool call is audit-logged.

## AI & Discovery

- [LLM site index (this property)](https://api.foodweb.network/llms.txt): Curated index for AI assistants, answer engines, and retrieval crawlers.
- [Food Web Kitchens (main marketplace) — LLM index](https://foodweb.network/llms.txt)
- [Food Web Maps — LLM index](https://maps.foodweb.network/llms.txt)
- [Food Web Community Forum — LLM index](https://forum.foodweb.network/llms.txt)
- [Food Web Partner Portal — LLM index](https://partners.foodweb.network/llms.txt)

## Documentation & Guides

- [MCP Server Overview](https://api.foodweb.network/mcp): What the Food Web MCP server is, the tool catalog, access tiers, and FAQ for connecting AI agents.
- [MCP Server Guide](https://api.foodweb.network/docs/mcp): Endpoint, authentication (fw_ API keys), role tiers, full tool reference, auditing and limits.
- [Authentication & Getting Started](https://api.foodweb.network/docs): How to authenticate with a Firebase ID token, make your first request, and handle errors.
- [API Endpoint Reference](https://api.foodweb.network/reference): Interactive OpenAPI reference for all Platform API endpoints.
- [Platform API Base URL](https://api.foodweb.network/v1): Live REST API root — all endpoints are under `/v1/`.
- [API Overview (Main Site)](https://foodweb.network/api): Marketing overview of the open food data API, map embeds, and developer ecosystem on the main product site.
- [Food Web Kitchens (Main Site)](https://foodweb.network): Commercial kitchen rental marketplace powered by the Platform API.
- [About Food Web](https://foodweb.network/about): Company mission and the broader Food Web ecosystem.
- [Contact](https://foodweb.network/contact): Support and developer inquiries.

## Products & Tools

- [API Portal Home](https://api.foodweb.network): Developer portal landing with endpoint group overview and quickstart code samples.
- [Developer Dashboard](https://api.foodweb.network/dashboard): Mint and revoke fw_ API keys, view your Firebase ID token (live API credential), usage overview, and quickstart links.
- [MCP Connect Page](https://api.foodweb.network/dashboard/mcp): Copy-paste MCP configs for Claude Code, Cursor, and Claude Desktop.
- [MCP Endpoint](https://mcp.foodweb.network): The live MCP protocol endpoint (POST JSON-RPC; other methods return 405).
- [Developer Quickstart](https://api.foodweb.network/dashboard/quickstart): Step-by-step guide to making authenticated API calls.
- [Developer Sign Up](https://api.foodweb.network/signup): Create a Food Web developer account (Firebase Auth).
- [Developer Log In](https://api.foodweb.network/login): Sign in to the developer dashboard.
- [Map & Discovery](https://api.foodweb.network/reference#map): Public endpoints to query places and food entities by viewport — no auth required, keyset-paginated.
- [Bookings & Availability](https://api.foodweb.network/reference#bookings): Register bookables, manage availability, create orders, approve bookings, and submit ratings.
- [Payments](https://api.foodweb.network/reference#payments): Stripe PaymentIntents and Checkout Sessions with credit application at checkout.
- [Credits & Grants](https://api.foodweb.network/reference#credits): Renter grants, partner pools, balances, invites, and the credit ledger.
- [Referrals & Partners](https://api.foodweb.network/reference#referrals): Referral codes, click tracking, conversions, and partner self-serve endpoints.
- [Messaging](https://api.foodweb.network/reference#messaging): Send messages and manage conversations (realtime reads via Firestore inbox mirror).
- [Suggestions](https://api.foodweb.network/reference#suggestions): Submit proposed map edits for moderation by verified contributors.
- [Moderation](https://api.foodweb.network/reference#admin): Curator read endpoints for suggestions, entities, places, and dedupe lookup (platform-admin routes are not published here).
- [Food Web Maps App](https://maps.foodweb.network): Standalone map app consuming map discovery endpoints.
- [Partner Portal](https://partners.foodweb.network): Partner-facing dashboard using credits and referrals API domains.

## Optional

- [Food Web Community Forum](https://forum.foodweb.network): Community Q&A — forum data is accessed via Platform API `/v1/forum/*` routes.
- [Research Library](https://foodweb.network/research): Reports on local food systems and open data.
- [Blog](https://foodweb.network/blog): Food Web stories and API-related product updates.
- [Terms of Service](https://foodweb.network/terms): Platform terms of use.
- [Privacy Policy](https://foodweb.network/privacy): Data collection and protection practices.