BillGO website screenshot

BillGO

BillGO is a Fort Collins, Colorado bill-payment technology company founded in 2015 that operates a real-time payments network connecting financial institutions, fintechs and billers. Its BillGO Exchange platform lets billers of any size receive electronic payments over ACH and one-time-use virtual cards instead of paper checks, and lets banks and credit unions embed real-time bill pay into their own applications. The Exchange web application at exchange.billgo.com is driven by a live GraphQL API with Okta-hosted OpenID Connect sign-in; the developer reference at docs.billgo.com is a private ReadMe project that redirects anonymous visitors to a login.

BillGO publishes 1 API on the APIs.io network. Tagged areas include Payments, Bill Pay, Financial Services, Banking, and ACH.

BillGO’s developer surface includes engineering blog, support, signup flow, authentication, and 15 more developer resources.

32.4/100 thin ▬ flat Agent 9/100 agent aware Full breakdown ↓
scored 2026-08-17 · rubric v0.11.0
1 APIs
PaymentsBill PayFinancial ServicesBankingACHVirtual CardsFintechGraphQL

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-17 · rubric v0.11.0
Composite quality — 32.4/100 · thin
Contract Quality 0.0 / 21
Developer Ergonomics 3.0 / 17
Commercial Clarity 8.5 / 17
Operational Transparency 2.9 / 11
Governance 1.3 / 10
Discoverability 7.4 / 9
Regulatory Posture 9.4 / 15
Agent readiness — 9/100 · agent aware
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 10
MCP Server 0 / 12
Machine-Readable Auth 10 / 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
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/billgo: 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 1

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

BillGO Exchange GraphQL API

The GraphQL API behind the BillGO Exchange biller portal. A live graphql-java server answers POST requests at https://exchange.billgo.com/graphql; schema introspection is disabl...

Security Posture 3

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

Billgo Authentication

openIdConnect/oauth2 · 2 schemes

SECURITY

Billgo Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Billgo Trust Center

SOC 2 Type II, SOC 1 Type I, PCI DSS Level 1 (via service providers)

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Billgo Scopes

8 scopes · authorizationCode

8 scopes

SCOPES

Resources

Get Started 2

Portal, sign-up, and the first successful call

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Access & Security 6

Authentication, authorization, and security posture

Operate 2

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

Source (apis.yml)

apis.yml Raw ↑
aid: billgo
name: BillGO
description: BillGO is a Fort Collins, Colorado bill-payment technology company founded in 2015 that operates a real-time
  payments network connecting financial institutions, fintechs and billers. Its BillGO Exchange platform lets billers of any
  size receive electronic payments over ACH and one-time-use virtual cards instead of paper checks, and lets banks and credit
  unions embed real-time bill pay into their own applications. The Exchange web application at exchange.billgo.com is driven
  by a live GraphQL API with Okta-hosted OpenID Connect sign-in; the developer reference at docs.billgo.com is a private ReadMe
  project that redirects anonymous visitors to a login.
image: https://billgo.com/hubfs/raw_assets/public/Billgo_January2023/images/Logo_Deep_Full.svg
url: https://raw.githubusercontent.com/api-evangelist/billgo/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.20'
created: '2026-08-07'
modified: '2026-08-07'
tags:
- Payments
- Bill Pay
- Financial Services
- Banking
- ACH
- Virtual Cards
- Fintech
- GraphQL
apis:
- name: BillGO Exchange GraphQL API
  description: The GraphQL API behind the BillGO Exchange biller portal. A live graphql-java server answers POST requests
    at https://exchange.billgo.com/graphql; schema introspection is disabled by the server, so no SDL could be captured. Authentication
    is Okta-hosted OpenID Connect via https://exchange-login.billgo.com/oauth2/default.
  humanURL: https://docs.billgo.com/
  baseURL: https://exchange.billgo.com/graphql
  tags:
  - GraphQL
  - Payments
  - Bill Pay
  properties:
  - type: Login
    url: https://exchange.billgo.com/login
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: TrustCenter
  url: security/billgo-trust-center.yml
- type: DomainSecurity
  url: security/billgo-domain-security.yml
- type: Website
  url: https://billgo.com/
- type: Blog
  url: https://billgo.com/blog
- type: Support
  url: https://billgo.com/contact
- type: SignUp
  url: https://start.billgo.com/
- type: Login
  url: https://exchange.billgo.com/login
- type: TermsOfService
  url: https://billgo.com/terms-and-conditions
- type: PrivacyPolicy
  url: https://billgo.com/privacy-policy
- type: Security
  url: https://billgo.com/security
- type: Compliance
  url: https://billgo.com/security
- type: StatusPage
  url: https://billgo.statuspage.io/
- type: WellKnown
  url: well-known/billgo-well-known.yml
- type: Authentication
  url: authentication/billgo-authentication.yml
- type: OAuthScopes
  url: scopes/billgo-scopes.yml
- type: Conformance
  url: conformance/billgo-conformance.yml
- type: Conventions
  url: conventions/billgo-conventions.yml
- type: Lifecycle
  url: lifecycle/billgo-lifecycle.yml
- type: LLMsTxt
  url: llms/billgo-llms.txt
x-enrichment:
  date: '2026-08-07'
  status: minimal
  artifacts_added: 10
  pass: local-v1
x-coverage:
  state: gated
  reason: partner-login
  detail: docs.billgo.com — the only BillGO developer reference — is a private ReadMe project that answers every path, including
    /reference and /openapi.json, with an HTTP 302 to https://dash.readme.com/to/billgo-group, so no contract, endpoint list
    or auth guide is readable without a BillGO account; the live GraphQL endpoint at exchange.billgo.com/graphql confirms
    the API exists but returns "Introspection has been disabled for this request".
  evidence:
  - url: https://docs.billgo.com/reference
    status: 302
  - url: https://docs.billgo.com/openapi.json
    status: 302
  - url: https://exchange.billgo.com/graphql
    status: 200
  - url: https://billgo.com/developers
    status: 404
  checked: '2026-08-07'