Slice

Slice is a done-for-you online ordering, marketing, payments, and point-of-sale platform for independent pizzerias, serving more than 19,000 shops across all 50 states and 3,000+ cities. Consumers order through slicelife.com and the Slice apps; shop owners run their business through slice.com, the Owner's Portal (owners.slicelife.com), and the Slice Register POS. Slice does publish a developer portal titled "Slice Public API" at developer.slicelife.com (built on Stoplight) and a separate merchant/banking API portal at developer.slicebank.com, but neither is an open, self-serve API - there is no public API-key signup and the endpoint reference is not openly rendered or documented for third parties. API access is partner-gated and arranged through Slice's partnerships team (partner@slicelife.com). The APIs listed below are logical groupings modeled from the platform's known merchant surfaces (shops, menus, orders, customers); no public OpenAPI definition is available, so no specification is included.

Slice publishes 4 APIs on the APIs.io network. Tagged areas include Online Ordering, Food Delivery, Pizzerias, Restaurant, and Point-of-Sale.

Slice’s developer surface includes documentation, signup flow, pricing, engineering blog, and 6 more developer resources.

10.5/100 minimal ▬ flat Agent 0/100 human only Full breakdown ↓
scored 2026-08-25 · rubric v0.14.0
4 APIs
Online OrderingFood DeliveryPizzeriasRestaurantPoint-of-SalePaymentsSMBPartner API

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-25 · rubric v0.14.0
Composite quality — 10.5/100 · minimal
Contract Quality 0.0 / 21
Developer Ergonomics 2.0 / 17
Access Clarity 4.0 / 17
Operational Transparency 0.3 / 11
Contract Governance 0.0 / 10
Discoverability 5.5 / 9
Regulatory Posture 1.4 / 15
Agent readiness — 0/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 10
Documented Reversibility 0 / 6
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 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 Surface 0 / 5
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.
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/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/slice-ordering: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 4

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

Slice Shops API (Modeled)

Logical, modeled grouping for the pizzeria (shop) records that anchor the Slice platform - profile, address, hours, service areas, and pickup/delivery availability. Reflected in...

Slice Menu API (Modeled)

Logical, modeled grouping for a shop's menu - categories, items, sizes, toppings, and pricing (the Owner's Portal exposes shop menu items at owners.slicelife.com/shops/{id}/menu...

Slice Orders API (Modeled)

Logical, modeled grouping for online orders placed for pickup or delivery - cart, checkout, order status, and fulfillment. Central to Slice's per-order commercial model (a flat ...

Slice Customers API (Modeled)

Logical, modeled grouping for the diner accounts, order history, and marketing/loyalty relationships that Slice manages on behalf of shops (consumer identity is handled via Auth...

Security Posture 1

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

Slice Ordering Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Resources

Get Started 1

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 1

Authentication, authorization, and security posture

Commercial 1

Pricing, plans, and the legal terms of use

Company 4

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: slice-ordering
url: https://raw.githubusercontent.com/api-evangelist/slice-ordering/refs/heads/main/apis.yml
name: Slice
kind: company
description: Slice is a done-for-you online ordering, marketing, payments, and point-of-sale platform for independent pizzerias,
  serving more than 19,000 shops across all 50 states and 3,000+ cities. Consumers order through slicelife.com and the Slice
  apps; shop owners run their business through slice.com, the Owner's Portal (owners.slicelife.com), and the Slice Register
  POS. Slice does publish a developer portal titled "Slice Public API" at developer.slicelife.com (built on Stoplight) and
  a separate merchant/banking API portal at developer.slicebank.com, but neither is an open, self-serve API - there is no
  public API-key signup and the endpoint reference is not openly rendered or documented for third parties. API access is partner-gated
  and arranged through Slice's partnerships team (partner@slicelife.com). The APIs listed below are logical groupings modeled
  from the platform's known merchant surfaces (shops, menus, orders, customers); no public OpenAPI definition is available,
  so no specification is included.
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source: []
  generated: '2026-07-22'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/slice-ordering.png
tags:
- Online Ordering
- Food Delivery
- Pizzerias
- Restaurant
- Point-of-Sale
- Payments
- SMB
- Partner API
tags_raw:
- Online Ordering
- Food Delivery
- Pizzerias
- Restaurants
- Point of Sale
- Payments
- SMB
- Partner API
created: '2026-07-04'
modified: '2026-07-04'
specificationVersion: '0.23'
apis:
- aid: slice-ordering:slice-shops-api
  name: Slice Shops API (Modeled)
  tags:
  - Shops
  - Restaurant
  - Merchants
  tags_raw:
  - Shops
  - Restaurants
  - Merchants
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://developer.slicelife.com/
  properties:
  - url: https://developer.slicelife.com/
    type: Documentation
  description: Logical, modeled grouping for the pizzeria (shop) records that anchor the Slice platform - profile, address,
    hours, service areas, and pickup/delivery availability. Reflected in the Owner's Portal shop surfaces (owners.slicelife.com/shops).
    No public endpoint reference is documented; access is partner-gated. Endpoints are modeled, not sourced from an OpenAPI
    definition.
- aid: slice-ordering:slice-menu-api
  name: Slice Menu API (Modeled)
  tags:
  - Menus
  - Item
  - Catalog
  tags_raw:
  - Menu
  - Items
  - Catalog
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://developer.slicelife.com/
  properties:
  - url: https://developer.slicelife.com/
    type: Documentation
  description: Logical, modeled grouping for a shop's menu - categories, items, sizes, toppings, and pricing (the Owner's
    Portal exposes shop menu items at owners.slicelife.com/shops/{id}/menu/items). No public endpoint reference is documented;
    access is partner-gated. Endpoints are modeled, not sourced from an OpenAPI definition.
- aid: slice-ordering:slice-orders-api
  name: Slice Orders API (Modeled)
  tags:
  - Order
  - Checkout
  - Fulfillment
  tags_raw:
  - Orders
  - Checkout
  - Fulfillment
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://developer.slicelife.com/
  properties:
  - url: https://developer.slicelife.com/
    type: Documentation
  description: Logical, modeled grouping for online orders placed for pickup or delivery - cart, checkout, order status, and
    fulfillment. Central to Slice's per-order commercial model (a flat per-order fee to the shop rather than a percentage).
    No public endpoint reference is documented; access is partner-gated. Endpoints are modeled, not sourced from an OpenAPI
    definition.
- aid: slice-ordering:slice-customers-api
  name: Slice Customers API (Modeled)
  tags:
  - Customers
  - Account
  - Loyalty
  tags_raw:
  - Customers
  - Accounts
  - Loyalty
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://developer.slicelife.com/
  properties:
  - url: https://developer.slicelife.com/
    type: Documentation
  description: Logical, modeled grouping for the diner accounts, order history, and marketing/loyalty relationships that Slice
    manages on behalf of shops (consumer identity is handled via Auth0). No public endpoint reference is documented; access
    is partner-gated. Endpoints are modeled, not sourced from an OpenAPI definition.
common:
- type: DomainSecurity
  url: security/slice-ordering-domain-security.yml
- type: GitHubOrganization
  url: https://github.com/slicelife
- type: LinkedIn
  url: https://www.linkedin.com/company/slice
- type: Website
  url: https://slicelife.com
- type: Website
  url: https://slice.com
- type: Documentation
  url: https://developer.slicelife.com/
- type: Documentation
  url: https://developer.slicebank.com/
- type: SignUp
  url: https://slice.com/get-started/
- type: Pricing
  url: https://slice.com/pricing/
- url: https://blog.slicelife.com/
  type: Blog
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

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/slice-ordering"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/slice-ordering/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/slice-ordering/evidence"

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

Get an API key

Free tier, no email required.

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