Receptapi Se ReceptAPI
57
AI ReadinessFoundational (C+)57/100
Official vendor OpenAPI document · agent-readyData EnrichmentData TransformationapiKey5 EndpointsREST
For Agents
Search and read Swedish recipes with ingredients, amounts, steps, EU 14 allergens, and timings, and look up ingredient data such as allergens and density for unit conversion.
Use for: Find a Swedish recipe that uses lingonberries, Get the full ingredient list and steps for a kanelbullar recipe, Check which allergens a recipe contains, Search for vegetarian dinner recipes
Not supported: Does not create or edit recipes, plan meals, order groceries, or give medical allergy advice. Use for reading Swedish recipe and ingredient data only.
The ReceptAPI API serves Swedish recipes as structured data, with ingredients, the EU 14 allergens, cooking steps, and serving information. Recipes can be listed by free text, category, tag, or ingredient, or fetched in full by slug with amounts, units, nutrition, difficulty, and total and active minutes. An ingredient endpoint returns each ingredient's Swedish name, allergens, default unit, density in grams per decilitre, and its Livsmedelsverket id. Free-tier use requires the attribution line returned in every response's meta block.
Install Jentic One Beta
Connect the ReceptAPI to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ReceptAPI, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Freceptapi.se%2Freceptapi" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Freceptapi.se%2Freceptapi" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with ReceptAPI API.
Search Swedish recipes by free text across titles, descriptions, tags, and ingredients
Filter the recipe list by category, tag, or an ingredient slug such as a specific vegetable
Fetch a full recipe by slug with ingredient amounts, units, groups, steps, nutrition, and allergens
Look up an ingredient's allergens, default_unit, density_g_per_dl, and livsmedelsverket_id
Find ingredients by Swedish name or alias and see how many recipes use each one
Use Cases
Patterns agents use ReceptAPI API for, with concrete tasks.
★ Allergy-aware cooking assistant through Jentic
A meal-planning agent asked for a dinner without milk or gluten needs real recipes with declared allergens rather than guesses. Through Jentic the agent searches for 'find a Swedish recipe', loads the ReceptAPI recipe search and detail operations with their input schemas, and reads the allergens array on each candidate recipe, with the optional API key injected at call time. It can then present only recipes whose allergens exclude mjolk and gluten, along with the required attribution line.
Call GET /recipes with q 'middag' and limit 20, then GET /recipes/{slug} for each result and keep only recipes whose allergens include neither 'mjolk' nor 'gluten'
Ingredient-led recipe discovery
A food app suggests what to cook from what is already in the fridge. ReceptAPI filters the recipe list by an ingredient slug, and the ingredients endpoint resolves a Swedish name or alias to that slug and reports how many recipes use it. The app chains the two to show matching recipes with servings, total_minutes, and difficulty.
Call GET /ingredients with q 'potatis' to get the ingredient slug, then GET /recipes with ingredient set to that slug and limit 10
Grams-and-decilitres unit conversion
Swedish recipes measure dry goods in decilitres, while nutrition and shopping tools often need grams. ReceptAPI returns density_g_per_dl and default_unit for each ingredient, so a tool can convert a recipe's amounts between volume and weight with the vendor's own figures rather than a generic table.
Call GET /ingredients/{slug} for 'vetemjol' and multiply 3 dl by density_g_per_dl to return the weight in grams
Key Endpoints
5 endpoints — the receptapi api serves swedish recipes as structured data, with ingredients, the eu 14 allergens, cooking steps, and serving information.
METHOD
PATH
DESCRIPTION
GET
/recipes
List recipes by text, category, tag, or ingredient
GET
/recipes/{slug}
Get a full recipe
GET
/search
Search recipes
GET
/ingredients
List ingredients by name or alias
GET
/ingredients/{slug}
Get an ingredient
GET
/recipes
List recipes by text, category, tag, or ingredient
GET
/recipes/{slug}
Get a full recipe
GET
/search
Search recipes
GET
/ingredients
List ingredients by name or alias
GET
/ingredients/{slug}
Get an ingredient
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
R
ReceptAPI
- Foundational (C+)57/100
100
Foundational Compliance63
Developer Experience & Jentic Compatibility37
AI-Readiness & Agent Experience94
Agent Usability50
Security50
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
100
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
2%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
37
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
15%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
80%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
55%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
50
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: C-Signals: 1
50%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring ReceptAPI by hand means deciding whether to send a key in the x-api-key header, tracking the daily call caps, and carrying the attribution line from meta into what you display. Through Jentic you install once, import ReceptAPI from the API Directory, store the key once, and your agent calls it.
Permission scoping
ReceptAPI is read-only and puts the recipe or ingredient slug in the URL path (/recipes/{slug}), so a rule can bound your agent to the read operations you pick, down to one recipe if you want. You choose which of the five operations it may call.
Credential isolation
If you use a ReceptAPI key, it is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'find a Swedish recipe' or 'get an ingredient's allergens', and Jentic returns the matching ReceptAPI operation with its input schema, including the q, category, tag, and ingredient filters.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using ReceptAPI API through Jentic.
What authentication does ReceptAPI use?
Per its OpenAPI spec, ReceptAPI takes an optional API key in the x-api-key header, and its security block also allows anonymous calls. The spec states anonymous calls get 50 a day per IP and a free key raises that to 100 a day. Through Jentic the key, if you use one, is stored by your own instance and attached at call time.
What are the rate limits for ReceptAPI?
The spec's own description states the limits: anonymous calls are capped at 50 a day per IP, and a free API key allows 100 a day. Check https://receptapi.se/ for any paid tiers above that.
Do I need to credit ReceptAPI when I use its data?
Yes, on the free tier. The spec states that all free-tier use requires attribution, and every response carries the required credit text, naming ReceptAPI and receptapi.se, in meta.attribution. Show that line wherever your agent displays the recipe.
Is there a ReceptAPI MCP server?
You don't need an MCP server to give your agent ReceptAPI. Jentic connects it directly from the API Directory: import it, store your key once if you have one, and your agent calls the recipe and ingredient operations on demand without loading extra tool definitions into its context.
How do I get a recipe's allergens through Jentic?
Search Jentic for 'get a Swedish recipe with allergens', load the GET /recipes/{slug} operation, and run it with the recipe slug. The response carries an allergens array using codes such as gluten, mjolk, and agg, along with the ingredient list. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Can I limit what my agent is allowed to do with ReceptAPI?
Yes. For example, write a rule that allows only GET /recipes and GET /recipes/{slug}, so the agent can search and read recipes but not page through the ingredient database, and every call it makes is logged.
GET STARTED