Brick

Brick builds payment infrastructure for modern money movement across Southeast Asia, starting with payouts and payment acceptance in Indonesia. It offers APIs for payments, payouts, compliance, and financial services, targeting businesses and developers seeking seamless integration of modern payment solutions in the region.

Brick is listed with 1 API on the APIs.io network. Tagged areas include Fintech, Payments, Southeast Asia, and B2B.

The Brick catalog on APIs.io includes 1 JSON-LD context and 1 Spectral governance ruleset.

Brick’s developer surface includes authentication, pricing, getting-started guide, documentation, API reference, and 22 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

43.6/100 developing Agent 25/100 agent aware Full breakdown ↓
scored 2026-10-23 · rubric v0.25.0 · Show this score on your site →

1 API

Fintech Payments Southeast Asia B2B

Kin Score

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

Composite quality — 43.6/100 · developing

Contract Quality 5.7 / 21

Developer Ergonomics 8.5 / 17

Access Clarity 10.7 / 17

Operational Transparency 2.9 / 11

Contract Governance 3.4 / 10

Discoverability 4.9 / 9

Regulatory Posture 4.2 / 15

Agent readiness — 25/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 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 0 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 4 / 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/onebrick/"><img src="https://apis.io/badge/onebrick/card.svg" alt="Brick 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/onebrick: 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 1

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

Brick API

Brick API as documented publicly: 6 operations. Contract generated from the documentation by API Evangelist (2026-10-21); not the provider's own document.

Pricing Plans 1

Published pricing tiers and plan structures.

Onebrick Plans Pricing

3 plans

PLANS

Semantic Vocabularies 1

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

Onebrick Context

7 classes · 16 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Brick API Rules

14 rules · 13 errors 1 info

SPECTRAL

JSON Schema 6

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

GetV2PaymentsAuthTokenResponse

4 properties

JSON SCHEMA

GetV2PaymentsGsBalanceResponse

4 properties

JSON SCHEMA

GetV2PaymentsGsGetTopUpHistoryResponse

20 properties

JSON SCHEMA

GetV2PaymentsGsLedgerResponse

4 properties

JSON SCHEMA

GetV2PaymentsGsTopUpBankListResponse

4 properties

JSON SCHEMA

PostV2PaymentsGsAcceptanceEwalletRequest

4 properties

JSON SCHEMA

Security Posture 3

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

Onebrick Authentication

1 scheme

SECURITY

Onebrick Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Onebrick Vulnerability Disclosure

security.txt · contact published

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

GettingStarted

GettingStarted

DeveloperPortal

DeveloperPortal

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

WellKnown

WellKnown

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Spectral

JSONLD

Vocabulary

DataModel

Conventions

Conformance

Access & Security 7

Authentication, authorization, and security posture

SecurityTxt

Security

Authentication

SecurityTxt

SecurityTxt

VulnerabilityDisclosure

VulnerabilityDisclosure

DomainSecurity

DomainSecurity

Scroll for all 7

Operate 1

Status, limits, changes, and where to get help

StatusPage

StatusPage

Commercial 4

Pricing, plans, and the legal terms of use

Plans

TermsOfService

PrivacyPolicy

Pricing

Company 1

The organization behind the API

Website

Website

Other 2

Properties that don't map to a standard resource type

Hosts

Hosts

Vendors

Vendors

Source (apis.yml)

aid: onebrick
name: Brick
image: https://www.onebrick.io/images/og.png
description: Brick builds payment infrastructure for modern money movement across Southeast Asia, starting with payouts and
  payment acceptance in Indonesia. It offers APIs for payments, payouts, compliance, and financial services, targeting businesses
  and developers seeking seamless integration of modern payment solutions in the region.
url: https://raw.githubusercontent.com/api-evangelist/onebrick/refs/heads/main/apis.yml
x-type: company
x-source: harvest:g2-catalog
x-tier: profiled
x-tier-reason: enrichment pass 2026-10-21 (modular-v1; was harvest)
specificationVersion: '0.20'
created: '2026-10-21'
modified: '2026-10-21'
tags:
- Fintech
- Payments
- Southeast Asia
- B2B
tags_raw:
- FinTech
- Payments
- Southeast Asia
- API
- B2B
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: SecurityTxt
  url: well-known/onebrick-onebrick-security.txt
- type: Plans
  url: plans/onebrick-plans-pricing.yml
- type: Spectral
  url: rules/onebrick-rules.yml
- type: JSONLD
  url: json-ld/onebrick-context.jsonld
- type: Vocabulary
  url: vocabulary/onebrick-vocabulary.yml
- type: DataModel
  url: data-model/onebrick-data-model.yml
- type: Conventions
  url: conventions/onebrick-conventions.yml
- type: Security
  url: https://www.onebrick.io/bug-report
- type: Authentication
  url: authentication/onebrick-authentication.yml
- type: Conformance
  url: conformance/onebrick-conformance.yml
- type: LLMsTxt
  url: llms/onebrick-llms.txt
- type: SecurityTxt
  url: well-known/onebrick-www-security.txt
- type: SecurityTxt
  url: well-known/onebrick-security.txt
- type: WellKnown
  url: well-known/onebrick-well-known.yml
- type: Hosts
  url: hosts/onebrick-hosts.yml
- type: Vendors
  url: vendors/onebrick-vendors.yml
- type: TermsOfService
  url: https://www.onebrick.io/terms
- type: StatusPage
  url: https://status.onebrick.io
- type: PrivacyPolicy
  url: https://www.onebrick.io/privacy
- type: Pricing
  url: https://www.onebrick.io/pricing
- type: GettingStarted
  url: https://docs.onebrick.io/transaction-history/getting-started
- type: Documentation
  url: https://docs.onebrick.io/
- type: DeveloperPortal
  url: https://api.onebrick.io</option
- type: APIReference
  url: https://docs.onebrick.io/api/authentication
- type: VulnerabilityDisclosure
  url: security/onebrick-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/onebrick-domain-security.yml
- type: Website
  url: https://onebrick.io/
apis:
- aid: onebrick:onebrick-api
  name: Brick API
  description: 'Brick API as documented publicly: 6 operations. Contract generated from the documentation by API Evangelist
    (2026-10-21); not the provider''s own document.'
  humanURL: https://docs.onebrick.io/th/api
  baseURL: https://sandbox.onebrick.io
  properties:
  - type: OpenAPI
    url: openapi/_ae-authored/onebrick-openapi-generated.yml
    x-provenance: generated
  - type: JSONSchema
    url: json-schema/onebrick-get-v2-payments-gs-get-top-up-history-response-schema.json
  - type: JSONSchema
    url: json-schema/onebrick-get-v2-payments-gs-ledger-response-schema.json
  - type: JSONSchema
    url: json-schema/onebrick-get-v2-payments-gs-balance-response-schema.json
  - type: JSONSchema
    url: json-schema/onebrick-get-v2-payments-gs-top-up-bank-list-response-schema.json
  - type: JSONSchema
    url: json-schema/onebrick-get-v2-payments-auth-token-response-schema.json
  - type: JSONSchema
    url: json-schema/onebrick-post-v2-payments-gs-acceptance-ewallet-request-schema.json
x-enrichment:
  date: '2026-10-21'
  status: enriched
  artifacts_added: 28
  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/onebrick"

All providers

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

Every operation they expose

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

How their score was established

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