EatStreet

EatStreet is a Madison, Wisconsin online food ordering and delivery marketplace, founded in 2010, that connects diners with local restaurants for takeout and delivery across US college towns and midsize metros, and sells restaurants an ordering, menu and point-of-sale integration platform on the merchant side. It once ran a documented public API — restaurant search, menus, order placement and tracking, and user management — at api.eatstreet.com/publicapi/v1, documented at developers.eatstreet.com. That surface is retired: the documentation host and every documented v1 path now return 404, though the company GitHub organization still points developers at the dead portal. What remains live is an OAuth 2.0 protected v2 API on the consumer host, whose only public, machine-readable contract is the RFC 8414 authorization server metadata EatStreet serves at /.well-known/oauth-authorization-server, advertising merchant_integration and customer scopes with PKCE.

EatStreet is listed with 1 API on the APIs.io network. Tagged areas include Company, Food Delivery, Restaurant, Online Ordering, and Marketplace.

EatStreet’s developer surface includes engineering blog, support, authentication, and 17 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

19.1/100 emerging ▬ flat Agent 8/100 agent aware Front door AI 1/6 silent Heartbeat 0/100 dormant saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessSelf serve

1 API

Company Food Delivery Restaurant Online Ordering Marketplace Local Commerce Consumer Point-of-Sale OAuth Authentication

Kin Score

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

Composite quality — 19.1/100 · emerging

Contract Quality 0.0 / 21

Developer Ergonomics 2.4 / 17

Access Clarity 3.6 / 17

Operational Transparency 0.3 / 11

Contract Governance 1.9 / 10

Discoverability 5.6 / 9

Regulatory Posture 5.1 / 15

Agent readiness — 8/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 7 / 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 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/eatstreet/"><img src="https://apis.io/badge/eatstreet/card.svg" alt="EatStreet 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
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link

10 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
Developer Ergonomics scores 14.3 — up to +17.1 composite points
Access Clarity scores 21.1 — up to +15.8 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/eatstreet/apis.yml: open an issue on github.com/api-evangelist/eatstreet 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 →

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.

OAuth

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.

EatStreet API v2

The live EatStreet API, served under https://eatstreet.com/api/v2 and protected by OAuth 2.0 authorization code with PKCE. EatStreet publishes no reference, no OpenAPI and no de...

EatStreet API pricing

Pricing Plans 1

Published pricing tiers and plan structures.

Eatstreet Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Eatstreet Rate Limits

0 limits

RATE LIMITS

Security Posture 2

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

Eatstreet Authentication

1 scheme

SECURITY

Eatstreet Domain Security

TLSv1.2 · HSTS · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Eatstreet Scopes

3 scopes

SCOPES

Resources

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

WellKnown

WellKnown

LLMsTxt

LLMsTxt

Design & Contract 4

Pagination, idempotency, versioning, errors, and events

Conformance

Conventions

ErrorCatalog

Lifecycle

Build 2

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Packages

Packages

Access & Security 3

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

OAuthScopes

OAuthScopes

Operate 2

Status, limits, changes, and where to get help

Support

Support

RateLimits

RateLimits

Commercial 3

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Plans

Plans

Company 3

The organization behind the API

Blog

Blog

Website

Website

Blog

Blog

Other 1

Properties that don't map to a standard resource type

SecondaryMarket

SecondaryMarket

Source (apis.yml)

aid: eatstreet
name: EatStreet
description: 'EatStreet is a Madison, Wisconsin online food ordering and delivery marketplace, founded in 2010, that connects
  diners with local restaurants for takeout and delivery across US college towns and midsize metros, and sells restaurants
  an ordering, menu and point-of-sale integration platform on the merchant side. It once ran a documented public API — restaurant
  search, menus, order placement and tracking, and user management — at api.eatstreet.com/publicapi/v1, documented at developers.eatstreet.com.
  That surface is retired: the documentation host and every documented v1 path now return 404, though the company GitHub organization
  still points developers at the dead portal. What remains live is an OAuth 2.0 protected v2 API on the consumer host, whose
  only public, machine-readable contract is the RFC 8414 authorization server metadata EatStreet serves at /.well-known/oauth-authorization-server,
  advertising merchant_integration and customer scopes with PKCE.'
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: self-serve
  trial: false
  try_now: false
  public: false
  gated: none
  gated_source:
  - onboarding
  label: Self-serve signup
  confidence: medium
  probe_state: covered
  source:
  - authentication
  - scopes
  - rate-limits
  - security
  generated: '2026-11-06'
  method: derived
image: https://eatstreet.com/apple-touch-icon.png
url: https://raw.githubusercontent.com/api-evangelist/eatstreet/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
x-tier: stub
x-tier-reason: harvest
specificationVersion: '0.23'
created: '2026-08-12'
modified: '2026-10-06'
tags:
- Company
- Food Delivery
- Restaurant
- Online Ordering
- Marketplace
- Local Commerce
- Consumer
- Point-of-Sale
- OAuth
- Authentication
tags_raw:
- Company
- Food Delivery
- Restaurants
- Online Ordering
- Marketplace
- Local Commerce
- Consumer
- Point of Sale
- OAuth
- Authentication
apis:
- name: EatStreet API v2
  description: The live EatStreet API, served under https://eatstreet.com/api/v2 and protected by OAuth 2.0 authorization
    code with PKCE. EatStreet publishes no reference, no OpenAPI and no developer portal for it; the only public contract
    is the RFC 8414 authorization server metadata, which names the authorize, token, introspection and revocation endpoints
    and the three advertised scopes (merchant_integration, customer, example). The router is live and answers unauthenticated
    probes with structured JSON errors, but the resource path space is undiscoverable without credentials.
  humanURL: https://eatstreet.com/
  baseURL: https://eatstreet.com/api/v2
  tags:
  - Online Ordering
  - Restaurant
  - OAuth
  - Authentication
  tags_raw:
  - Online Ordering
  - Restaurants
  - OAuth
  - Authentication
  properties:
  - type: Authentication
    url: authentication/eatstreet-authentication.yml
  - type: OAuthScopes
    url: scopes/eatstreet-scopes.yml
  - type: ErrorCatalog
    url: errors/eatstreet-problem-types.yml
  - type: RateLimits
    url: rate-limits/eatstreet-rate-limits.yml
  - type: Conventions
    url: conventions/eatstreet-conventions.yml
  - type: Lifecycle
    url: lifecycle/eatstreet-lifecycle.yml
  - type: Plans
    url: plans/eatstreet-plans-pricing.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- url: https://eatstreet.com/blog/
  type: Blog
- type: DomainSecurity
  url: security/eatstreet-domain-security.yml
- type: Website
  url: https://eatstreet.com/
- type: SecondaryMarket
  url: https://forgeglobal.com/eatstreet_stock/
- type: Support
  url: https://help.eatstreet.com/
- type: Blog
  url: https://blog.eatstreet.com/
- type: TermsOfService
  url: https://eatstreet.com/terms
- type: PrivacyPolicy
  url: https://eatstreet.com/app/Legal.jsp
- type: GitHubOrganization
  url: https://github.com/eatstreet
- type: WellKnown
  url: well-known/eatstreet-well-known.yml
- type: Authentication
  url: authentication/eatstreet-authentication.yml
- type: OAuthScopes
  url: scopes/eatstreet-scopes.yml
- type: Conformance
  url: conformance/eatstreet-conformance.yml
- type: Conventions
  url: conventions/eatstreet-conventions.yml
- type: ErrorCatalog
  url: errors/eatstreet-problem-types.yml
- type: Lifecycle
  url: lifecycle/eatstreet-lifecycle.yml
- type: Packages
  url: packages/eatstreet-packages.yml
- type: Plans
  url: plans/eatstreet-plans-pricing.yml
- type: RateLimits
  url: rate-limits/eatstreet-rate-limits.yml
- type: LLMsTxt
  url: llms/eatstreet-llms.txt
x-enrichment:
  date: '2026-08-12'
  status: enriched
  artifacts_added: 14
  pass: local-v1
x-coverage:
  state: covered
  reason: no-machine-readable-spec
  detail: EatStreet still serves a real RFC 8414 OAuth authorization server metadata document and JWKS on eatstreet.com, but
    its developer portal developers.eatstreet.com returns 404 and every path of the documented v1 public API under api.eatstreet.com/publicapi
    now 404s, so the live v2 API has no published reference and no OpenAPI, GraphQL SDL, AsyncAPI or MCP manifest on any host.
  evidence:
  - url: https://eatstreet.com/.well-known/oauth-authorization-server
    status: 200
  - url: https://developers.eatstreet.com/
    status: 404
  - url: https://api.eatstreet.com/publicapi/v1
    status: 404
  - url: https://eatstreet.com/api/v2/oauth/token
    status: 401
  checked: '2026-08-12'

EatStreet API — frequently asked questions

Does EatStreet have an API?

Yes. APIs.io lists 1 API from EatStreet, including EatStreet API v2.

How do I authenticate with the EatStreet API?

EatStreet uses bearer-token authentication (1 scheme). The details are profiled on APIs.io as Eatstreet Authentication.

Is the EatStreet API ready for AI agents?

EatStreet has a Kin Score of 19.1 out of 100 (emerging) and an Agent Readiness score of 7.9 (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/eatstreet"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/eatstreet/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.