Blink Ledger Systems website screenshot

Blink Ledger Systems

Blink (Blink Ledger Systems Inc.) builds online identity and payment technologies for digital publishers. A single Blink account works across publishers, giving readers one universal login and frictionless payment so they can subscribe, donate, or buy an individual article or podcast with one click, or enable autopay for small frequent purchases. Publishers integrate three products — Blink Identity, Blink Pay and Blink Donate — through one hosted JavaScript SDK that places Blink-managed panels into the page, a dashboard-configured User Journeys rules engine, four server-side JSON endpoints for OAuth2 login, and a signed webhook notification stream covering subscription, payment and donation events. Founded 2017; incorporated in the US in 2018 and surfaced in the API Evangelist network as a Polychain portfolio company.

Blink Ledger Systems publishes 5 API contracts indexed on the APIs.io network, including Authentication API, OAuth Applications API, Users API, and 2 more. Tagged areas include Company, Infrastructure, Payments, Identity, and Authentication.

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

Blink Ledger Systems’ developer surface includes engineering blog, documentation, API reference, getting-started guide, support, signup flow, authentication, and 27 more developer resources.

34.1/100 thin ▬ flat Agent 27/100 agent aware Front door AI 1/6 silent saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →
1 published contract 2 Agent Skills
CompanyInfrastructurePaymentsIdentityAuthenticationPublishingMediaSubscriptionDonationsMicropaymentsPaywallWebhook

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0
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. Kin Score badge preview for Blink Ledger Systems It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/blink-ledger-systems/"><img src="https://apis.io/badge/blink-ledger-systems/card.svg" alt="Blink Ledger Systems 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
  • 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
  • Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
  • Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
  • Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
7 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
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/blink-ledger-systems/apis.yml: open an issue on github.com/api-evangelist/blink-ledger-systems 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.

MarketPositionDepthRegistered MCP serverDeclares compatibility
x402 Micropayments & Agentic Pay-per-Call 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.

measured — observed by APIs.io (published)

APIs 5

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

Blink SDK for JavaScript

Browser SDK exposing window.blinkSDK. Provides Login with Blink (getAuthorizationCode), subscription entitlement checks (isSubscribed, getSubscription, onSubscriptionChange), si...

Blink Notifications (Webhooks)

Outbound webhook stream delivering signed JSON notifications for subscription, payment and donation lifecycle events. Every payload is signed with ed25519 over the canonicalized...

Blink Ledger Systems Authentication API

Client account login and bearer token issuance.

Blink Ledger Systems OAuth Applications API

Registration and retrieval of OAuth application credentials.

Blink Ledger Systems Users API

Blink user profile exchange.

Open Collections 3

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

Agent Skills 2

Packaged agent skills for driving this provider's APIs from an AI assistant.

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

Event Specifications 1

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

Semantic Vocabularies 1

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

Blink Ledger Systems Context

7 classes · 14 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Blink Ledger Systems API Rules

13 rules · 11 errors 1 warnings 1 info

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.

Blink Ledger Systems Server Side Api Overlay

8 actions · update

DERIVED

JSON Schema 6

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

AccessTokenRequest

5 properties

JSON SCHEMA

LoginRequest

2 properties

JSON SCHEMA

LoginToken

1 properties

JSON SCHEMA

OAuthApplicationConfig

3 properties

JSON SCHEMA

RegisterApplicationRequest

2 properties

JSON SCHEMA

UserProfileResponse

1 properties

JSON SCHEMA

Security Posture 2

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

Agentic Access 1

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

Blink Ledger Systems Agentic Access

4 operations · 2 acting

4 operations · 2 acting

AGENTIC

Resources

Get Started 4

Portal, sign-up, and the first successful call

Documentation 3

Reference material describing how the API behaves

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 10

Pagination, idempotency, versioning, errors, and events

Scroll for all 10

Build 2

SDKs, sample code, and the tooling you integrate with

Access & Security 2

Authentication, authorization, and security posture

Operate 3

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Other 3

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: blink-ledger-systems
name: Blink Ledger Systems
description: Blink (Blink Ledger Systems Inc.) builds online identity and payment technologies for digital publishers. A single
  Blink account works across publishers, giving readers one universal login and frictionless payment so they can subscribe,
  donate, or buy an individual article or podcast with one click, or enable autopay for small frequent purchases. Publishers
  integrate three products — Blink Identity, Blink Pay and Blink Donate — through one hosted JavaScript SDK that places Blink-managed
  panels into the page, a dashboard-configured User Journeys rules engine, four server-side JSON endpoints for OAuth2 login,
  and a signed webhook notification stream covering subscription, payment and donation events. Founded 2017; incorporated
  in the US in 2018 and surfaced in the API Evangelist network as a Polychain portfolio company.
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: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
image: https://blink.net/resources/favicon.png
url: https://raw.githubusercontent.com/api-evangelist/blink-ledger-systems/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- polychain
x-tier: profiled
x-tier-reason: enriched-from-public-docs
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-10-06'
x-docs-platform: docusaurus
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-09-20
tags:
- Company
- Infrastructure
- Payments
- Identity
- Authentication
- Publishing
- Media
- Subscription
- Donations
- Micropayments
- Paywall
- Webhook
tags_raw:
- Company
- Infrastructure
- Payments
- Identity
- Authentication
- OAuth
- Publishing
- Media
- Subscriptions
- Donations
- Micropayments
- Paywall
- Webhooks
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Deprecation
  url: lifecycle/blink-ledger-systems-lifecycle.yml
- type: AgenticAccess
  url: agentic-access/blink-ledger-systems-agentic-access.yml
- type: Spectral
  url: rules/blink-ledger-systems-rules.yml
- type: JSONLD
  url: json-ld/blink-ledger-systems-context.jsonld
- type: Vocabulary
  url: vocabulary/blink-ledger-systems-vocabulary.yml
- type: Hosts
  url: hosts/blink-ledger-systems-hosts.yml
- type: Vendors
  url: vendors/blink-ledger-systems-vendors.yml
- url: https://blink.net/blog/
  type: Blog
- type: X-MCPServerCandidate
  url: mcp/blink-ledger-systems-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: Website
  url: https://blink.net
- type: DeveloperPortal
  url: https://docs.blink.net/
- type: Documentation
  url: https://docs.blink.net/docs/getting-started/overview.html
- type: APIReference
  url: https://docs.blink.net/docs/api-reference/functions.html
- type: GettingStarted
  url: https://docs.blink.net/docs/getting-started/quick-start.html
- type: Support
  url: https://docs.blink.net/docs/getting-started/support.html
- type: SignUp
  url: https://blink.net/login
- type: TermsOfService
  url: https://blink.net/terms
- type: PrivacyPolicy
  url: https://blink.net/privacy-policy
- type: StatusPage
  url: https://status.blink.net
- type: OpenAPI
  url: openapi/_ae-authored/blink-ledger-systems-server-side-api-openapi.yml
- type: Overlay
  url: overlays/blink-ledger-systems-server-side-api-overlay.yaml
- type: Packages
  url: packages/blink-ledger-systems-packages.yml
- type: SDKs
  url: packages/blink-ledger-systems-packages.yml
- type: Authentication
  url: authentication/blink-ledger-systems-authentication.yml
- type: ErrorCatalog
  url: errors/blink-ledger-systems-problem-types.yml
- type: Conventions
  url: conventions/blink-ledger-systems-conventions.yml
- type: Lifecycle
  url: lifecycle/blink-ledger-systems-lifecycle.yml
- type: Sandbox
  url: sandbox/blink-ledger-systems-sandbox.yml
- type: Components
  url: components/blink-ledger-systems-components.yml
- type: DataModel
  url: data-model/blink-ledger-systems-data-model.yml
- type: Webhooks
  url: asyncapi/blink-ledger-systems-notifications-webhooks.yml
- type: Conformance
  url: conformance/blink-ledger-systems-conformance.yml
- type: AgentSkill
  url: skills/_index.yml
- type: DomainSecurity
  url: security/blink-ledger-systems-domain-security.yml
apis:
- aid: blink-ledger-systems:blink-ledger-systems-sdk
  name: Blink SDK for JavaScript
  description: Browser SDK exposing window.blinkSDK. Provides Login with Blink (getAuthorizationCode), subscription entitlement
    checks (isSubscribed, getSubscription, onSubscriptionChange), single-article charging (requestPayment), hosted donation
    and subscription modals, and the variables/functions extension points that dashboard-configured User Journeys evaluate
    against.
  humanURL: https://docs.blink.net/docs/api-reference/load-blink-sdk.html
  baseURL: https://blink.net/1.0
  tags:
  - Payments
  - Identity
  - Subscription
  - Donations
  tags_raw:
  - Payments
  - Identity
  - Subscriptions
  - Donations
  properties:
  - type: Documentation
    url: https://docs.blink.net/docs/api-reference/load-blink-sdk.html
  - type: APIReference
    url: https://docs.blink.net/docs/api-reference/functions.html
  - type: SDKs
    url: packages/blink-ledger-systems-packages.yml
  - type: Components
    url: components/blink-ledger-systems-components.yml
- aid: blink-ledger-systems:blink-ledger-systems-notifications
  name: Blink Notifications (Webhooks)
  description: Outbound webhook stream delivering signed JSON notifications for subscription, payment and donation lifecycle
    events. Every payload is signed with ed25519 over the canonicalized event object, with an optional Blink-Echo-Token shared-secret
    header.
  humanURL: https://docs.blink.net/docs/notifications/webHooks.html
  baseURL: https://api.blink.net
  tags:
  - Webhook
  - Event
  - Payments
  tags_raw:
  - Webhooks
  - Events
  - Payments
  properties:
  - type: Webhooks
    url: asyncapi/blink-ledger-systems-notifications-webhooks.yml
  - type: Documentation
    url: https://docs.blink.net/docs/notifications/webHooks.html
- aid: blink-ledger-systems:blink-ledger-systems-authentication-api
  name: Blink Ledger Systems Authentication API
  description: Client account login and bearer token issuance.
  humanURL: https://docs.blink.net/docs/server-side-api/api-overview.html
  baseURL: https://api.blink.net
  tags:
  - Authentication
  properties:
  - type: OpenAPI
    url: openapi/blink-ledger-systems-authentication-api-openapi.yml
  - type: Documentation
    url: https://docs.blink.net/docs/server-side-api/api-overview.html
  - type: APIReference
    url: https://docs.blink.net/docs/server-side-api/api-overview.html
  - type: Authentication
    url: authentication/blink-ledger-systems-authentication.yml
  - type: ErrorCatalog
    url: errors/blink-ledger-systems-problem-types.yml
  - type: JSONSchema
    url: json-schema/blink-ledger-systems-login-request-schema.json
  - type: JSONSchema
    url: json-schema/blink-ledger-systems-login-token-schema.json
- aid: blink-ledger-systems:blink-ledger-systems-oauth-applications-api
  name: Blink Ledger Systems OAuth Applications API
  description: Registration and retrieval of OAuth application credentials.
  humanURL: https://docs.blink.net/docs/server-side-api/api-overview.html
  baseURL: https://api.blink.net
  tags:
  - OAuth Applications
  properties:
  - type: OpenAPI
    url: openapi/blink-ledger-systems-oauth-applications-api-openapi.yml
  - type: Documentation
    url: https://docs.blink.net/docs/server-side-api/api-overview.html
  - type: APIReference
    url: https://docs.blink.net/docs/server-side-api/api-overview.html
  - type: Authentication
    url: authentication/blink-ledger-systems-authentication.yml
  - type: ErrorCatalog
    url: errors/blink-ledger-systems-problem-types.yml
  - type: JSONSchema
    url: json-schema/blink-ledger-systems-oauth-application-config-schema.json
  - type: JSONSchema
    url: json-schema/blink-ledger-systems-register-application-request-schema.json
- aid: blink-ledger-systems:blink-ledger-systems-users-api
  name: Blink Ledger Systems Users API
  description: Blink user profile exchange.
  humanURL: https://docs.blink.net/docs/server-side-api/api-overview.html
  baseURL: https://api.blink.net
  tags:
  - User
  tags_raw:
  - Users
  properties:
  - type: OpenAPI
    url: openapi/blink-ledger-systems-users-api-openapi.yml
  - type: Documentation
    url: https://docs.blink.net/docs/server-side-api/api-overview.html
  - type: APIReference
    url: https://docs.blink.net/docs/server-side-api/api-overview.html
  - type: Authentication
    url: authentication/blink-ledger-systems-authentication.yml
  - type: ErrorCatalog
    url: errors/blink-ledger-systems-problem-types.yml
  - type: JSONSchema
    url: json-schema/blink-ledger-systems-access-token-request-schema.json
  - type: JSONSchema
    url: json-schema/blink-ledger-systems-user-profile-response-schema.json
x-not-published:
  notes: 'Probed and confirmed absent, recorded so later runs do not re-search: no /.well-known/ documents on any host (all
    soft-404 — see well-known/blink-ledger-systems-well-known.yml), no llms.txt, no robots.txt, no AsyncAPI document, no public
    GitHub organization, no MCP server (a candidate tool list is derived in mcp/), no CLI, no changelog or release notes,
    no roadmap, no pricing page, no blog, no Postman collection, no published rate limits, no OAuth scope registry, no security.txt
    or vulnerability disclosure program, no trust center or named certifications, and no decline-code reference. Deliberately
    no Idempotency, Deprecation, Security, Compliance, MCPServer or WellKnown pointer is wired, because Blink publishes none
    of those things.'
x-enrichment:
  date: '2026-10-20'
  status: enriched
  artifacts_added: 0
  pass: local-v5

Blink Ledger Systems API — frequently asked questions

Does Blink Ledger Systems have an API?

Yes. APIs.io lists 5 APIs from Blink Ledger Systems, including Blink SDK for JavaScript, Blink Notifications (Webhooks) and Blink Ledger Systems Authentication API, and 2 more.

Is there an OpenAPI specification for the Blink Ledger Systems API?

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

How do I authenticate with the Blink Ledger Systems API?

Blink Ledger Systems uses bearer-token authentication (6 schemes). The details are profiled on APIs.io as Blink Ledger Systems Authentication.

Is the Blink Ledger Systems API ready for AI agents?

Blink Ledger Systems has a Kin Score of 34.1 out of 100 (thin) and an Agent Readiness score of 26.7 (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/blink-ledger-systems"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/blink-ledger-systems/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/blink-ledger-systems/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.

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