Lavu

Lavu is a cloud-based iPad restaurant point-of-sale system, now positioned as an AI-powered restaurant intelligence platform, serving restaurants, bars, and hospitality businesses with POS, payments, inventory, and reporting. Lavu promotes an open API that lets developers and restaurants extend the point of sale, build peripheral components, and create tailored integrations without waiting on vendor roadmaps. The POSLavu API is a POST-based interface where a single request server accepts form-encoded credentials (dataname, key, token) plus a table selector and returns XML rows; documented tables include menu_groups, menu_categories, menu_items, tables, orders, order_contents, order_payments, ingredients, and ingredient_usage. Records can be written with cmd=insert and an XML contents payload. Credentials are retrieved from the API tab of the POSLavu Control Panel, and the developer documentation is published at admin.poslavu.com; API access comes with an active Lavu account.

Lavu publishes 2 APIs on the APIs.io network: Menu API and Orders API. Tagged areas include Restaurant, Point-of-Sale, Payments, Inventory, and Menu Management.

The Lavu catalog on APIs.io includes 1 JSON-LD context and 2 Spectral governance rulesets.

Lavu’s developer surface includes authentication, engineering blog, pricing, and 10 more developer resources.

🌐 Visit website 📡 Source on GitHub

27.1/100 thin ▬ flat Agent 25/100 agent aware saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0

AccessPaid

2 APIs

Restaurant Point-of-Sale Payments Inventory Menu Management

Kin Score

Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0

Composite quality — 27.1/100 · thin

Contract Quality 4.0 / 19

Developer Ergonomics 3.2 / 15

Access Clarity 5.9 / 15

Operational Transparency 2.1 / 10

Contract Governance 2.6 / 9

Discoverability 3.8 / 8

Regulatory Posture 4.0 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 25/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 7 / 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

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.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. 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/.

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 github.com/api-evangelist/lavu: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 2

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

Lavu Menu API

Menu groups, categories, and items.

Lavu Orders API

Orders, order contents, and payments.

Open Collections 6

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

API Collection

OPEN COLLECTION

Lavu (POSLavu) Inventory API

OPEN COLLECTION

Lavu (POSLavu) Inventory Menu API

OPEN COLLECTION

Lavu (POSLavu) Inventory Orders API

OPEN COLLECTION

Lavu (POSLavu) API

OPEN COLLECTION

Lavu (POSLavu) Inventory Tables API

OPEN COLLECTION

Pricing Plans 1

Published pricing tiers and plan structures.

Lavu Plans Pricing

4 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Lavu Rate Limits

1 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Lavu Finops

FINOPS

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Lavu Poslavu Api Context

7 classes · 161 properties

JSON-LD

Spectral Rules 2

Spectral governance rulesets for linting and validating these APIs.

Lavu API Rules

5 rules · 4 warnings 1 info

SPECTRAL

Lavu API Rules

35 rules · 4 errors 22 warnings 9 info

SPECTRAL

JSON Schema 7

Standalone JSON Schema definitions for this provider's data models.

MenuCategory

16 properties

JSON SCHEMA

MenuGroup

4 properties

JSON SCHEMA

MenuItem

32 properties

JSON SCHEMA

OrderContent

41 properties

JSON SCHEMA

OrderPayment

47 properties

JSON SCHEMA

Order

58 properties

JSON SCHEMA

Table

8 properties

JSON SCHEMA

Scroll for all 7

JSON Structure 7

JSON Structure definitions describing this provider's data shapes.

Poslavu Api Menu Category Structure

16 properties

JSON STRUCTURE

Poslavu Api Menu Group Structure

4 properties

JSON STRUCTURE

Poslavu Api Menu Item Structure

32 properties

JSON STRUCTURE

Poslavu Api Order Content Structure

41 properties

JSON STRUCTURE

Poslavu Api Order Payment Structure

47 properties

JSON STRUCTURE

Poslavu Api Order Structure

58 properties

JSON STRUCTURE

Poslavu Api Table Structure

8 properties

JSON STRUCTURE

Scroll for all 7

Examples 7

Example request and response payloads for these APIs.

Poslavu Api Menu Category Example

16 fields

EXAMPLE

Poslavu Api Menu Group Example

4 fields

EXAMPLE

Poslavu Api Menu Item Example

32 fields

EXAMPLE

Poslavu Api Order Content Example

41 fields

EXAMPLE

Poslavu Api Order Example

58 fields

EXAMPLE

Poslavu Api Order Payment Example

47 fields

EXAMPLE

Poslavu Api Table Example

8 fields

EXAMPLE

Scroll for all 7

Security Posture 2

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

Lavu Authentication

apiKey · 1 scheme

SECURITY

Lavu Domain Security

TLSv1.3 · DMARC

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Lavu Agentic Access

2 operations · 2 acting

AGENTIC

Resources

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Rules

Rules

Vocabulary

Vocabulary

JSONLD

JSONLD

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Operate 1

Status, limits, changes, and where to get help

RateLimits

RateLimits

Commercial 3

Pricing, plans, and the legal terms of use

Pricing

Pricing

Plans

Plans

FinOps

FinOps

Company 3

The organization behind the API

Website

Website

Blog

Blog

LinkedIn

Source (apis.yml)

aid: lavu
name: Lavu
description: Lavu is a cloud-based iPad restaurant point-of-sale system, now positioned as an AI-powered restaurant intelligence
  platform, serving restaurants, bars, and hospitality businesses with POS, payments, inventory, and reporting. Lavu promotes
  an open API that lets developers and restaurants extend the point of sale, build peripheral components, and create tailored
  integrations without waiting on vendor roadmaps. The POSLavu API is a POST-based interface where a single request server
  accepts form-encoded credentials (dataname, key, token) plus a table selector and returns XML rows; documented tables include
  menu_groups, menu_categories, menu_items, tables, orders, order_contents, order_payments, ingredients, and ingredient_usage.
  Records can be written with cmd=insert and an XML contents payload. Credentials are retrieved from the API tab of the POSLavu
  Control Panel, and the developer documentation is published at admin.poslavu.com; API access comes with an active Lavu account.
type: Index
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: paid
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Paid
  confidence: medium
  source:
  - plans
  - authentication
  - security
  generated: '2026-09-03'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/lavu.png
tags:
- Restaurant
- Point-of-Sale
- Payments
- Inventory
- Menu Management
tags_raw:
- Restaurant
- Point of Sale
- Payments
- Inventory
- Menu Management
url: https://raw.githubusercontent.com/api-evangelist/lavu/refs/heads/main/apis.yml
created: '2026-06-02'
modified: '2026-06-02'
specificationVersion: '0.23'
apis:
- aid: lavu:lavu-menu-api
  name: Lavu Menu API
  description: Menu groups, categories, and items.
  tags:
  - Menus
  tags_raw:
  - Menu
  properties:
  - type: OpenAPI
    url: openapi/lavu-menu-api-openapi.yml
  - type: Documentation
    url: https://admin.poslavu.com/cp/areas/api_doc.html
  - type: Documentation
    url: https://lavu.com/integrations/
- aid: lavu:lavu-orders-api
  name: Lavu Orders API
  description: Orders, order contents, and payments.
  tags:
  - Order
  tags_raw:
  - Orders
  properties:
  - type: OpenAPI
    url: openapi/lavu-orders-api-openapi.yml
  - type: Documentation
    url: https://admin.poslavu.com/cp/areas/api_doc.html
  - type: Documentation
    url: https://lavu.com/integrations/
common:
- type: AgenticAccess
  url: agentic-access/lavu-agentic-access.yml
- type: DomainSecurity
  url: security/lavu-domain-security.yml
- type: Authentication
  url: authentication/lavu-authentication.yml
- type: Website
  url: https://lavu.com
- type: Blog
  url: https://lavu.com/blog/
- type: Pricing
  url: https://lavu.com/pricing/
- type: LinkedIn
  url: https://www.linkedin.com/company/lavu-inc
- type: Plans
  url: plans/lavu-plans-pricing.yml
- type: RateLimits
  url: rate-limits/lavu-rate-limits.yml
- type: FinOps
  url: finops/lavu-finops.yml
- type: Rules
  url: rules/lavu-spectral-rules.yml
- type: Vocabulary
  url: vocabulary/lavu-vocabulary.yaml
- type: JSONLD
  url: json-ld/lavu-poslavu-api-context.jsonld
x-common:
  features:
  - name: Open API
    description: POST-based table query and insert API for extending the POS and building peripheral components and integrations.
  - name: Menu Management
    description: Read menu groups, categories, and items, and insert new menu items.
  - name: Order Management
    description: Read orders, line items, and payments, and insert new orders, order contents, and payments.
  - name: Floor Layout
    description: Read the restaurant floor table layout (coordinates, shapes, names).
  - name: Inventory
    description: Read ingredients and ingredient usage data.
  - name: Payment Processing
    description: Integrated card payment processing with dual-pricing / cash-discount options to offset card fees.
  useCases:
  - name: Sales Reporting and Reconciliation
    description: Pull orders, order_contents, and order_payments to reconcile sales and payment volume against the POS and
      accounting systems.
  - name: Custom Online Ordering
    description: Read menu structure and insert orders to power a custom or third-party online ordering experience on top
      of Lavu.
  - name: Inventory and Recipe Costing
    description: Read ingredients and ingredient_usage to feed inventory tracking and recipe-costing tools.
  - name: Peripheral Integrations
    description: Build tailored integrations and peripheral components against the open POSLavu API without waiting on vendor
      roadmaps.
  integrations:
  - name: QuickBooks
    description: Accounting integration.
  - name: Xero
    description: Accounting integration.
  - name: Restaurant365
    description: Restaurant accounting and operations integration.
  - name: DoorDash
    description: Online ordering and delivery integration.
  - name: Grubhub
    description: Online ordering and delivery integration.
  - name: Uber Eats
    description: Online ordering and delivery integration.
  - name: Otter
    description: Online ordering aggregation integration.
  - name: Chowly
    description: Online ordering aggregation integration.
  - name: OpenTable
    description: Reservations and loyalty integration.
  - name: Marketman
    description: Inventory management integration.
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/lavu"

All providers

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

Every operation they expose

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

How their score was established

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