Jelly

Jelly (getjelly.co.uk) is an all-in-one costing and kitchen-management platform for the hospitality industry - restaurants and professional kitchens. It handles supplier invoice processing, ingredient and recipe costing, gross-profit (GP) analysis, menu and dish management, suppliers, products, purchase orders and stock. Jelly runs a GraphQL API at api.getjelly.co.uk (bearer-authenticated, public introspection, 232 queries and 168 mutations) behind its kitchen web app, and publishes a first-party UI component library (Jelly UI, @getjelly/jelly-ui). Surfaced originally as a Seedcamp portfolio company and enriched here from its live public surface.

Jelly is listed with 1 API on the APIs.io network. Tagged areas include Company, Hospitality, Restaurant, Kitchen Management, and Food Costing.

Jelly’s developer surface includes documentation, pricing, support, signup flow, authentication, and 17 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

34.1/100 thin ▬ flat Agent 17/100 agent aware Front door AI 3/6 light saas Full breakdown ↓
scored 2026-10-31 · rubric v0.25.0 · Show this score on your site →

1 API 3 Agent Skills

Company Hospitality Restaurant Kitchen ManagementFood CostingRecipe CostingInvoice Processing GraphQL Software-as-a-Service

Kin Score

Kin Score How this is scored →
scored 2026-10-31 · rubric v0.25.0

Composite quality — 34.1/100 · thin

Contract Quality 7.5 / 21

Developer Ergonomics 4.8 / 17

Access Clarity 7.6 / 17

Operational Transparency 1.2 / 11

Contract Governance 0.5 / 10

Discoverability 5.6 / 9

Regulatory Posture 4.6 / 15

Agent readiness — 17/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/jelly/"><img src="https://apis.io/badge/jelly/card.svg" alt="Jelly on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link

9 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 35.1 — up to +16.2 composite points
Developer Ergonomics scores 28.0 — up to +14.4 composite points
Operational Transparency scores 10.5 — up to +11.6 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/jelly/apis.yml: open an issue on github.com/api-evangelist/jelly to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
PDF and Document Standards (PDF tooling, document signing trust, invoice documents)	undeclared	-	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

GraphQL

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

Jelly GraphQL API

Jelly's GraphQL API for costing and kitchen management. Single POST endpoint at api.getjelly.co.uk with bearer-token auth and public introspection; exposes kitchens, ingredients...

Agent Skills 3

Packaged agent skills for driving this provider's APIs from an AI assistant.

Build a menu in Jelly

AGENT SKILL

Cost a recipe in Jelly

AGENT SKILL

Process a supplier invoice in Jelly

AGENT SKILL

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Jelly Authentication

http · 1 scheme

SECURITY

Jelly Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Jelly Vulnerability Disclosure

Hackerone · contact published

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

SignUp

SignUp

Login

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

GraphQL

GraphQL

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

X-MCPServerCandidate

X-MCPServerCandidate

AgentSkill

AgentSkill

LLMsTxt

LLMsTxt

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

DataModel

Components

Conformance

Build 1

SDKs, sample code, and the tooling you integrate with

Packages

Packages

Access & Security 4

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Security

Security

Authentication

Authentication

VulnerabilityDisclosure

VulnerabilityDisclosure

Operate 1

Status, limits, changes, and where to get help

Support

Support

Commercial 3

Pricing, plans, and the legal terms of use

Pricing

Pricing

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 1

The organization behind the API

Website

Website

Source (apis.yml)

aid: jelly
name: Jelly
description: Jelly (getjelly.co.uk) is an all-in-one costing and kitchen-management platform for the hospitality industry
  - restaurants and professional kitchens. It handles supplier invoice processing, ingredient and recipe costing, gross-profit
  (GP) analysis, menu and dish management, suppliers, products, purchase orders and stock. Jelly runs a GraphQL API at api.getjelly.co.uk
  (bearer-authenticated, public introspection, 232 queries and 168 mutations) behind its kitchen web app, and publishes a
  first-party UI component library (Jelly UI, @getjelly/jelly-ui). Surfaced originally as a Seedcamp portfolio company and
  enriched here from its live public surface.
url: https://raw.githubusercontent.com/api-evangelist/jelly/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- seedcamp
x-tier: stub
x-tier-reason: portfolio-lead
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-09-03'
  method: derived
image: https://kitchen.getjelly.co.uk/icons/apple-touch-icon.png
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-19'
tags:
- Company
- Hospitality
- Restaurant
- Kitchen Management
- Food Costing
- Recipe Costing
- Invoice Processing
- GraphQL
- Software-as-a-Service
tags_raw:
- Company
- Hospitality
- Restaurants
- Kitchen Management
- Food Costing
- Recipe Costing
- Invoice Processing
- GraphQL
- SaaS
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis:
- name: Jelly GraphQL API
  description: Jelly's GraphQL API for costing and kitchen management. Single POST endpoint at api.getjelly.co.uk with bearer-token
    auth and public introspection; exposes kitchens, ingredients, recipes, dishes, menus, suppliers, products, invoices and
    purchase orders.
  humanURL: https://docs.getjelly.co.uk/
  baseURL: https://api.getjelly.co.uk/
  properties:
  - type: GraphQL
    url: graphql/jelly-api.graphql
  - type: Introspection
    url: graphql/jelly-api-introspection.json
  - type: Authentication
    url: authentication/jelly-authentication.yml
  - type: Conventions
    url: conventions/jelly-conventions.yml
  - type: ErrorCatalog
    url: errors/jelly-error-codes.yml
  - type: DataModel
    url: data-model/jelly-data-model.yml
  - type: X-MCPServerCandidate
    url: mcp/jelly-mcp.yml
    note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list
      derived from the published API contracts, not an existing server. The scorer already read the manifest and reported
      mcp_server correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
common:
- type: DomainSecurity
  url: security/jelly-domain-security.yml
- type: Website
  url: https://www.getjelly.co.uk/
- type: Documentation
  url: https://docs.getjelly.co.uk/
- type: Pricing
  url: https://www.getjelly.co.uk/pricing
- type: TermsOfService
  url: https://www.getjelly.co.uk/terms
- type: PrivacyPolicy
  url: https://www.getjelly.co.uk/privacy
- type: Support
  url: https://www.getjelly.co.uk/support
- type: SignUp
  url: https://kitchen.getjelly.co.uk/signup
- type: Login
  url: https://kitchen.getjelly.co.uk/signin
- type: Security
  url: https://www.getjelly.co.uk/security
- type: GraphQL
  url: graphql/jelly-api.graphql
- type: Authentication
  url: authentication/jelly-authentication.yml
- type: Conventions
  url: conventions/jelly-conventions.yml
- type: ErrorCatalog
  url: errors/jelly-error-codes.yml
- type: DataModel
  url: data-model/jelly-data-model.yml
- type: Packages
  url: packages/jelly-packages.yml
- type: Components
  url: components/jelly-components.yml
- type: X-MCPServerCandidate
  url: mcp/jelly-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: AgentSkill
  url: skills/_index.yml
- type: Conformance
  url: conformance/jelly-conformance.yml
- type: VulnerabilityDisclosure
  url: security/jelly-vulnerability-disclosure.yml
- type: LLMsTxt
  url: llms/jelly-llms.txt
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

Jelly API — frequently asked questions

Does Jelly have an API?

Yes. APIs.io lists 1 API from Jelly, including Jelly GraphQL API.

How do I authenticate with the Jelly API?

Jelly uses bearer-token authentication (http · 1 scheme). The details are profiled on APIs.io as Jelly Authentication.

Is the Jelly API ready for AI agents?

Jelly has a Kin Score of 34.1 out of 100 (thin) and an Agent Readiness score of 17.1 (agent-aware), scored by API Evangelist on 2026-10-31.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/jelly"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/jelly/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/jelly/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.