BILT

BILT is a financial technology company offering a loyalty and payments platform that lets members earn rewards on rent and mortgage payments. It provides a co‑branded credit card, rent‑payment reporting to credit bureaus, and a suite of neighborhood benefits, aiming to transform housing expenses into valuable points and perks for users.

BILT publishes 4 API contracts indexed on the APIs.io network, including Default payment method API, Headless payments API, One-time payments API, and 1 more. Tagged areas include Fintech, Loyalty, Payments, RentRewards, and Credit Cards.

The BILT catalog on APIs.io includes 1 event-driven AsyncAPI specification, 1 JSON-LD context, and 1 Spectral governance ruleset.

BILT’s developer surface includes documentation, API reference, and 16 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

18.0/100 emerging ▬ flat Agent 43/100 agent ready Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 published contract

Fintech Loyalty PaymentsRentRewardsCredit Cards Real Estate

Kin Score

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

Composite quality — 18.0/100 · emerging

Contract Quality 5.5 / 19

Developer Ergonomics 1.2 / 15

Access Clarity 0.6 / 15

Operational Transparency 0.8 / 10

Contract Governance 2.0 / 9

Discoverability 4.8 / 8

Regulatory Posture 1.8 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 43/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 9 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 6 / 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.

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/.

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/bilt/"><img src="https://apis.io/badge/bilt/card.svg" alt="BILT 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):

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
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)
Agent Skills +5 pts — skills artifact present, graded by who authored it

5 more unmet checks in the Agent Readiness table above.

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

Access Clarity scores 3.9 — up to +19.2 composite points
Developer Ergonomics scores 8.3 — up to +18.3 composite points
Contract Quality scores 29.1 — up to +17.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/bilt/apis.yml: open an issue on github.com/api-evangelist/bilt 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
Consumer Lending Licensing (UK, US, Canada credit licence registers)	undeclared	-	-	-

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.

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.

OpenAPI

measured — observed by APIs.io (published)

APIs 4

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

Bilt Checkout SDK

External backend contract for integrators using the Bilt Checkout SDK, documented at developers.bilt.com. No owned OpenAPI spec found on Bilt's own domain.

BILT Default payment method API

Read-only lookup of a customer's current default payment-method summary for display and pre-flight checks. Bilt resolves the default again at charge time, so it may change betwe...

BILT Headless payments API

Charge a customer's current default Bilt payment method with no Bilt UI, for subscriptions, autopay, or other off-session payments. The outcome arrives as a `payment.*` webhook.

BILT One-time payments API

Open a checkout session that renders Bilt-hosted checkout in the Checkout SDK. The customer confirms the payment themselves; the outcome arrives as a `checkout.session.*` webhook.

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Bilt Webhooks

ASYNCAPI

Semantic Vocabularies 1

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

Bilt Context

18 classes · 33 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs. Counts are the severity each rule declares, not results of running them.

BILT API Rules

17 rules · 15 error-severity 1 warn-severity 1 info-severity

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Bilt Overlay

1 action · update

DERIVED

Security Posture 1

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

Bilt Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Resources

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

Design & Contract 9

Pagination, idempotency, versioning, errors, and events

Spectral

JSONLD

Vocabulary

Webhooks

DataModel

Idempotency

Conventions

ErrorCatalog

Conformance

Scroll for all 9

Access & Security 2

Authentication, authorization, and security posture

TrustCenter

TrustCenter

DomainSecurity

DomainSecurity

Company 1

The organization behind the API

Website

Website

Other 3

Properties that don't map to a standard resource type

Overlay

Overlay

Hosts

Hosts

Vendors

Vendors

Source (apis.yml)

aid: bilt
name: BILT
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  probe_state: unreadable
  source:
  - security
  generated: '2026-11-06'
  method: derived
image: https://framerusercontent.com/assets/YTMxpEJv31tk1JFEEX3t2rIls.png
description: BILT is a financial technology company offering a loyalty and payments platform that lets members earn rewards
  on rent and mortgage payments. It provides a co‑branded credit card, rent‑payment reporting to credit bureaus, and a suite
  of neighborhood benefits, aiming to transform housing expenses into valuable points and perks for users.
url: https://raw.githubusercontent.com/api-evangelist/bilt/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:
- Fintech
- Loyalty
- Payments
- RentRewards
- Credit Cards
- Real Estate
tags_raw:
- FinTech
- Loyalty
- Payments
- RentRewards
- CreditCard
- RealEstate
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Spectral
  url: rules/bilt-rules.yml
- type: JSONLD
  url: json-ld/bilt-context.jsonld
- type: Vocabulary
  url: vocabulary/bilt-vocabulary.yml
- type: Webhooks
  url: asyncapi/bilt-webhooks.yml
- type: DataModel
  url: data-model/bilt-data-model.yml
- type: Idempotency
  url: conventions/bilt-conventions.yml
- type: Conventions
  url: conventions/bilt-conventions.yml
- type: ErrorCatalog
  url: errors/bilt-problem-types.yml
- type: Conformance
  url: conformance/bilt-conformance.yml
- type: Overlay
  url: overlays/bilt-overlay.yaml
- type: LLMsTxt
  url: llms/bilt-llms.txt
- type: Hosts
  url: hosts/bilt-hosts.yml
- type: Vendors
  url: vendors/bilt-vendors.yml
- type: TrustCenter
  url: https://trust.bilt.com/
- type: Documentation
  url: https://developers.bilt.com/
- type: APIReference
  url: https://developers.bilt.com/docs/
- type: DomainSecurity
  url: security/bilt-domain-security.yml
- type: Website
  url: https://www.bilt.com
apis:
- name: Bilt Checkout SDK
  description: External backend contract for integrators using the Bilt Checkout SDK, documented at developers.bilt.com. No
    owned OpenAPI spec found on Bilt's own domain.
  humanURL: https://developers.bilt.com/docs/
  aid: bilt:bilt-checkout-sdk
- aid: bilt:bilt-default-payment-method-api
  name: BILT Default payment method API
  description: 'Read-only lookup of a customer''s current default payment-method

    summary for display and pre-flight checks. Bilt resolves the default

    again at charge time, so it may change between lookup and payment.'
  humanURL: https://developers.bilt.com/docs/
  tags:
  - Default payment method
  properties:
  - type: OpenAPI
    url: openapi/bilt-default-payment-method-api-openapi.yml
- aid: bilt:bilt-headless-payments-api
  name: BILT Headless payments API
  description: 'Charge a customer''s current default Bilt payment method with no Bilt

    UI, for subscriptions, autopay, or other off-session payments. The

    outcome arrives as a `payment.*` webhook.'
  humanURL: https://developers.bilt.com/docs/
  tags:
  - Headless payments
  properties:
  - type: OpenAPI
    url: openapi/bilt-headless-payments-api-openapi.yml
- aid: bilt:bilt-one-time-payments-api
  name: BILT One-time payments API
  description: 'Open a checkout session that renders Bilt-hosted checkout in the

    Checkout SDK. The customer confirms the payment themselves; the

    outcome arrives as a `checkout.session.*` webhook.'
  humanURL: https://developers.bilt.com/docs/
  tags:
  - One-Time Payments
  tags_raw:
  - One-time payments
  properties:
  - type: OpenAPI
    url: openapi/bilt-one-time-payments-api-openapi.yml
x-coverage:
  state: unreadable
  reason: no-machine-readable-spec
  detail: The only OpenAPI spec found is hosted at partnerapi.biltrewards.com, not on Bilt's own domain.
  evidence:
  - url: https://developers.bilt.com/docs/specs/checkout-sdk.yml
    status: 200
  checked: '2026-09-28'
x-enrichment:
  date: '2026-09-28'
  status: enriched
  artifacts_added: 18
  pass: modular-v1
  engine: identity=local,contract=local,surfaces=local,docs=local,regulatory=local

BILT API — frequently asked questions

Does BILT have an API?

Yes. APIs.io lists 4 APIs from BILT, including Bilt Checkout SDK, BILT Default payment method API and BILT Headless payments API, and 1 more.

Is there an OpenAPI specification for the BILT API?

Yes. APIs.io indexes 3 OpenAPI specifications for BILT, each linked for download from this page.

Is the BILT API ready for AI agents?

BILT has a Kin Score of 18.0 out of 100 (emerging) and an Agent Readiness score of 42.9 (agent-ready), 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/bilt"

All providers

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

Every operation they expose

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

How their score was established

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