LevelUp

LevelUp (SCVNGR, Inc. d/b/a LevelUp) was a Boston-based mobile payments and customer-loyalty platform whose REST API let point-of-sale systems and e-commerce applications accept LevelUp payments, issue QR-code order tokens, manage merchant locations, and run merchant-funded loyalty and credit campaigns. The platform shipped first-party C#, Ruby and Java SDKs plus packaged point-of-sale adapters for Aloha, Micros 3700, Dinerware and Agilysys InfoGenesis. LevelUp was acquired by Grubhub in 2018 and the platform API is now RETIRED: the developer portal, API reference, sandbox and production hosts have all been decommissioned and thelevelup.com redirects to grubhub.com. This profile is a historical record reconstructed from LevelUp's surviving first-party open-source SDKs and package feeds.

LevelUp is profiled on the APIs.io network. Tagged areas include Company, Consumer, Payments, Mobile Payments, and Point-of-Sale.

LevelUp’s developer surface includes engineering blog, authentication, and 15 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

16.8/100 emerging ▬ flat Agent 5/100 agent aware Heartbeat 0/100 dormant self hosted · Apache-2.0 Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

0 APIs

Company Consumer Payments Mobile Payments Point-of-Sale Loyalty Restaurant Retired

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 16.8/100 · emerging

Contract Quality 0.0 / 19

Developer Ergonomics 3.2 / 15

Access Clarity 0.0 / 15

Operational Transparency 2.6 / 10

Contract Governance 1.6 / 9

Discoverability 4.2 / 8

Regulatory Posture 3.3 / 15

Open Source Surface 2.5 / 10

Agent readiness — 5/100 · agent aware

Machine-Readable Contract 0 / 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 0 / 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

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Payments 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.

Open Source Surface applies to this provider. This product is open source and we read its repository directly, so Open Source Surface carries 10 points of the composite. It is scored from what the repository actually publishes — a security policy, a contribution guide, a release history, a code of conduct — read live from the provider rather than inferred from our own catalog pointers. This facet adds; nothing was taken away to make room for it. An open-source project is not excused from the commercial facets, because exemption would strip it of the points it does earn. If we have the wrong repository, or this product is not open source, say so on your provider repo and we will drop the facet rather than have you publish against 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 75 points between them, because both conditional facets apply and carry 25 points together. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% 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/levelup/"><img src="https://apis.io/badge/levelup/card.svg" alt="LevelUp 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):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
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)

11 more unmet checks in the Agent Readiness table above.

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

Contract Quality scores 0.0 — up to +25.0 composite points
Access Clarity scores 0.0 — up to +20.0 composite points
Developer Ergonomics scores 21.4 — up to +15.7 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/levelup/apis.yml: open an issue on github.com/api-evangelist/levelup 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
Mobile SDK Publishers (Play SDK Index, CocoaPods, ADA certification)	builds-on	44.1	-	-

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.

Security Posture 2

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

Levelup Authentication

apiKey/custom-token · 4 schemes

SECURITY

Levelup Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

Design & Contract 4

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Lifecycle

Conformance

Build 4

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

SourceCode

Packages

SDKs

Access & Security 2

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

Operate 3

Status, limits, changes, and where to get help

IssueTracker

IssueTracker

Releases

Releases

Deprecation

Deprecation

Commercial 1

Pricing, plans, and the legal terms of use

License

License

Company 2

The organization behind the API

Blog

Blog

Website

Website

Source (apis.yml)

aid: levelup
name: LevelUp
description: 'LevelUp (SCVNGR, Inc. d/b/a LevelUp) was a Boston-based mobile payments and customer-loyalty platform whose
  REST API let point-of-sale systems and e-commerce applications accept LevelUp payments, issue QR-code order tokens, manage
  merchant locations, and run merchant-funded loyalty and credit campaigns. The platform shipped first-party C#, Ruby and
  Java SDKs plus packaged point-of-sale adapters for Aloha, Micros 3700, Dinerware and Agilysys InfoGenesis. LevelUp was acquired
  by Grubhub in 2018 and the platform API is now RETIRED: the developer portal, API reference, sandbox and production hosts
  have all been decommissioned and thelevelup.com redirects to grubhub.com. This profile is a historical record reconstructed
  from LevelUp''s surviving first-party open-source SDKs and package feeds.'
url: https://raw.githubusercontent.com/api-evangelist/levelup/refs/heads/main/apis.yml
deliveryModel:
  model: self-hosted
  license: Apache-2.0
  open_source: true
  commercial: false
  callable_host: false
  label: Self-hosted open source · you run it yourself
  confidence: high
  source:
  - license
  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
  - url: https://thelevelup.com
    status: 302
    note: declared website redirects to https://www.grubhub.com/ — a different registrable domain (thelevelup.com -> grubhub.com),
      possible rename or acquisition (probed 2026-09-03, roadmap#169)
  generated: '2026-11-06'
  method: derived
image: https://avatars.githubusercontent.com/u/1521628?v=4
x-type: company
x-source: vc-portfolio
x-backed-by:
- gv
x-tier: profiled
x-tier-reason: enriched-from-surviving-first-party-sdks
x-lifecycle-status: retired
x-acquired-by: Grubhub
x-acquisition-year: 2018
x-legal-entity: SCVNGR, Inc. d/b/a LevelUp
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-10-06'
tags:
- Company
- Consumer
- Payments
- Mobile Payments
- Point-of-Sale
- Loyalty
- Restaurant
- Retired
tags_raw:
- Company
- Consumer
- Payments
- Mobile Payments
- Point of Sale
- Loyalty
- Restaurants
- Retired
apis: []
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- url: https://www.grubhub.com/blog/
  type: Blog
- type: IssueTracker
  url: https://github.com/TheLevelUp/levelup-sdk-csharp/issues
- type: Releases
  url: https://github.com/TheLevelUp/levelup-sdk-csharp/releases
- type: License
  name: Apache-2.0
  url: https://github.com/TheLevelUp/levelup-sdk-csharp/blob/master/LICENSE
- type: Website
  url: https://thelevelup.com
- type: GitHubOrganization
  url: https://github.com/TheLevelUp
- type: SourceCode
  url: https://github.com/TheLevelUp/levelup-sdk-csharp
- type: Packages
  url: packages/levelup-packages.yml
- type: SDKs
  url: packages/levelup-packages.yml
- type: Authentication
  url: authentication/levelup-authentication.yml
- type: Conventions
  url: conventions/levelup-conventions.yml
- type: ErrorCatalog
  url: errors/levelup-problem-types.yml
- type: Lifecycle
  url: lifecycle/levelup-lifecycle.yml
- type: Deprecation
  url: lifecycle/levelup-lifecycle.yml
- type: Conformance
  url: conformance/levelup-conformance.yml
- type: DomainSecurity
  url: security/levelup-domain-security.yml
- type: LLMsTxt
  url: llms/levelup-llms.txt
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

LevelUp API — frequently asked questions

How do I authenticate with the LevelUp API?

LevelUp uses bearer-token authentication (apiKey/custom-token · 4 schemes). The details are profiled on APIs.io as Levelup Authentication.

Is the LevelUp API ready for AI agents?

LevelUp has a Kin Score of 16.8 out of 100 (emerging) and an Agent Readiness score of 5.4 (agent-aware), scored by API Evangelist on 2026-11-06.

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/levelup"

All providers

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

Every operation they expose

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

How their score was established

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

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.