# Tallow Index Tallow Index is a read-only, source-backed index of exact beef tallow skincare product variants. ## Agent entry points - Agent query contract: /agent-query-contract.v1.json - OpenAPI document: /openapi.json - Evidence-aware query: /api/v1/agent/query - Source-use and rights-review register: /api/v1/source-use-register - Product list: /api/v1/products - Human brand directory: /brands - Brand discovery list: /api/v1/brands - Exact product record: /api/v1/products/{variant-slug} - Immutable evidence receipt: /api/v1/releases/{release-id}/evidence/{variant-slug} - Public release changes as JSON Feed: /feeds/releases.json - Public release changes as RSS: /feeds/releases.xml - Stateless read-only MCP: /mcp - Human data catalog: /for-agents - Ingredient record list: /api/v1/ingredients - Canonical ingredient record: /api/v1/ingredients/{ingredient-slug} - Complete label ingredient list: /api/v1/label-ingredients - Label occurrence record: /api/v1/label-ingredients/{ingredient-slug} - Curated ingredient comparison: /api/v1/ingredient-comparisons/{comparison-slug} - Living Evidence Note list: /api/v1/notes - Current release answer for one note: /api/v1/notes/{note-slug} - Methodology: /methodology - Privacy and data use: /privacy Use exact variant IDs and slugs. The product catalog accepts only `q` for text search. Use `/api/v1/agent/query` for evidence, ingredient, and price filters. Discover canonical brand slugs at `/api/v1/brands`; the agent query also accepts normalized brand display names. Prefer `no_named_essential_oil_listed` over the legacy `essential_oil_free` name. This field describes released evidence and does not prove a complete formulation. Preserve raw ingredient labels, canonical mappings, evidence states, checked dates, conflicts, unknowns, release IDs, result hashes, and evidence links. A Living Evidence Note is a deterministic question over the current release. Its HTML and JSON answers use the same result. `/api/v1/ingredients` contains the smaller set of reviewed concepts with outside reference facts. `/api/v1/label-ingredients` contains every supported ingredient name in the current product release. A label occurrence does not prove benefits, safety, quality, amount, concentration, or performance. Do not infer medical effectiveness or treat an unknown fact as false. ## Query examples - Products that list beeswax: `/api/v1/agent/query?required_ingredient=beeswax` - Products that do not name an essential oil: `/api/v1/agent/query?no_named_essential_oil_listed=true` - Products at or below $15 USD per ounce: `/api/v1/agent/query?max_price_per_oz=15¤cy=USD` Parameter names are singular and repeatable. Use `required_ingredient=beeswax&required_ingredient=jojoba-oil` when every listed ingredient is required. `ingredient`, `ingredients`, and `required_ingredients` are not accepted. The endpoint is GET-only. Unknown fields fail with a 422 response so an agent cannot silently run a broader query. Evidence states are descriptive, not scores: verified, corroborated, single_source, conflicted, stale, unknown, and rejected. Source rights are tracked separately in `/api/v1/source-use-register`; `not_assessed` is a review exception and does not mean permission or legal clearance. The MCP endpoint accepts JSON over Streamable HTTP. It exposes only `query_products` and `get_evidence_receipt`. It uses the same deterministic query service and receipt serializer as REST. It cannot write data, call a model, fetch outside sources, or retain a session.