Billfold

Billfold provides a cashless and contactless point‑of‑sale operating system for live events. Built by operators for operators, it unifies payments, devices, POS terminals, and workflow data into a single platform, offering real‑time revenue control, streamlined reporting, and enhanced guest experiences across festivals, conferences, venues, and venues of all sizes. The solution supports RFID, NFC, and traditional card payments, delivering a flexible, scalable, and secure event‑payment ecosystem.

Billfold is listed with 1 API on the APIs.io network. Tagged areas include Payments, Event, Point-of-Sale, RFID, and Cashless.

Billfold’s developer surface includes documentation, engineering blog, pricing, support, and 11 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

24.6/100 emerging ▬ flat Agent 0/100 human only Full breakdown ↓
scored 2026-10-23 · rubric v0.25.0 · Show this score on your site →

1 API

Payments Event Point-of-Sale RFIDCashless

Kin Score

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

Composite quality — 24.6/100 · emerging

Contract Quality 0.0 / 21

Developer Ergonomics 4.5 / 17

Access Clarity 10.7 / 17

Operational Transparency 1.2 / 11

Contract Governance 0.0 / 10

Discoverability 5.5 / 9

Regulatory Posture 1.9 / 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 Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

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 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/billfold/"><img src="https://apis.io/badge/billfold/card.svg" alt="Billfold on APIs.io — Kin Score by API Evangelist"></a>

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

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/billfold: 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 →

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.

RFID

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.

Billfold API

API for Billfold point‑of‑sale platform

Pricing Plans 1

Published pricing tiers and plan structures.

Billfold Plans Pricing

17 plans

PLANS

Security Posture 1

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

Billfold Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 1

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

WellKnown

WellKnown

Access & Security 2

Authentication, authorization, and security posture

SecurityTxt

SecurityTxt

DomainSecurity

DomainSecurity

Operate 1

Status, limits, changes, and where to get help

Support

Support

Commercial 4

Pricing, plans, and the legal terms of use

Plans

TermsOfService

PrivacyPolicy

Pricing

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 2

Properties that don't map to a standard resource type

Hosts

Hosts

Vendors

Vendors

Source (apis.yml)

aid: billfold
name: Billfold
image: https://cdn.prod.website-files.com/625c9425341435b0290d74d6/62da651bcb63071d86513f26_Billfold-logotype-color-gradient-RGB.png
description: Billfold provides a cashless and contactless point‑of‑sale operating system for live events. Built by operators
  for operators, it unifies payments, devices, POS terminals, and workflow data into a single platform, offering real‑time
  revenue control, streamlined reporting, and enhanced guest experiences across festivals, conferences, venues, and venues
  of all sizes. The solution supports RFID, NFC, and traditional card payments, delivering a flexible, scalable, and secure
  event‑payment ecosystem.
url: https://raw.githubusercontent.com/api-evangelist/billfold/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
x-tier: profiled
x-tier-reason: enrichment pass 2026-09-28 (modular-v1; was harvest)
specificationVersion: '0.20'
created: '2026-09-28'
modified: '2026-09-28'
tags:
- Payments
- Event
- Point-of-Sale
- RFID
- Cashless
tags_raw:
- Payments
- Events
- POS
- RFID
- Cashless
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Plans
  url: plans/billfold-plans-pricing.yml
- type: LLMsTxt
  url: llms/billfold-llms.txt
- type: SecurityTxt
  url: well-known/billfold-help-security.txt
- type: WellKnown
  url: well-known/billfold-well-known.yml
- type: Hosts
  url: hosts/billfold-hosts.yml
- type: Vendors
  url: vendors/billfold-vendors.yml
- type: TermsOfService
  url: https://www.billfold.tech/tos
- type: PrivacyPolicy
  url: https://www.billfold.tech/privacy-policy
- type: DeveloperPortal
  url: https://portal.billfold.tech/
- type: DomainSecurity
  url: security/billfold-domain-security.yml
- type: Website
  url: https://www.billfold.tech/
- type: Documentation
  url: https://help.billfoldpos.com/
- type: Blog
  url: https://www.billfold.tech/blog
- type: Pricing
  url: https://www.billfold.tech/pricing
- type: Support
  url: https://help.billfoldpos.com/
apis:
- name: Billfold API
  description: API for Billfold point‑of‑sale platform
  humanURL: https://portal.billfold.tech/
  baseURL: null
  properties: []
  aid: billfold:billfold-api
x-coverage:
  state: unreadable
  reason: no-machine-readable-spec
  method: derived
  generated: '2026-09-28'
  generator: derive-coverage.py (pre-flight evidence)
  detail: the company publishes developer documentation but serves no machine-readable contract from it
  evidence:
  - url: https://portal.billfold.tech/mcp
    status: 403
  - url: https://www.nasdaqprivatemarket.com/
    status: 200
x-enrichment:
  date: '2026-09-28'
  status: enriched
  artifacts_added: 9
  pass: modular-v1
  engine: identity=local,contract=local,surfaces=local,docs=local,regulatory=local

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

All providers

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

Every operation they expose

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

How their score was established

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