Omise

Omise is a Singapore‑based payments platform that provides a simple, secure API for accepting online payments, managing recurring subscriptions, and handling payouts across multiple currencies. Founded in 2013, Omise serves merchants, developers, and enterprises in Southeast Asia and beyond, offering features such as fraud detection, tokenization, and comprehensive dashboard analytics. The company emphasizes developer‑friendly documentation, robust SDKs, and compliance with regional financial regulations.

Omise is listed with 1 API on the APIs.io network. Tagged areas include Company, Payments, API, FinTech, and Southeast-Asia.

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

Omise’s developer surface includes changelog, authentication, signup flow, pricing, engineering blog, getting-started guide, documentation, and 18 more developer resources.

42.6/100 developing Agent 20/100 agent aware Full breakdown ↓
scored 2026-10-31 · rubric v0.25.0 · Show this score on your site →
1 API
CompanyPaymentsAPIFinTechSoutheast-Asia

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-10-31 · rubric v0.25.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 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. Kin Score badge preview for Omise It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/opn-ooo/"><img src="https://apis.io/badge/opn-ooo/card.svg" alt="Omise 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
  • 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
  • Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
  • Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
10 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/opn-ooo/apis.yml: open an issue on github.com/api-evangelist/opn-ooo 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 →

APIs 1

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

Omise API

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

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.

Opn Ooo Context

12 classes · 58 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Omise API Rules

11 rules · 9 errors 1 warnings 1 info

SPECTRAL

JSON Schema 6

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

GetForexCurrencyResponse

6 properties

JSON SCHEMA

GetTokensIdResponse

8 properties

JSON SCHEMA

PatchCustomersIdCardsCardidRequest

5 properties

JSON SCHEMA

PostChargesIdRefundsResponse

14 properties

JSON SCHEMA

PostChargesRequest

21 properties

JSON SCHEMA

PostTokensResponse

8 properties

JSON SCHEMA

Security Posture 2

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

Opn Ooo Authentication

1 scheme

SECURITY

Opn Ooo Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 8

Pagination, idempotency, versioning, errors, and events

Scroll for all 8

Access & Security 3

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 3

The organization behind the API

Other 2

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: opn-ooo
name: Omise
image: https://cdn.prod.website-files.com/67481ca1f2e8301c5e5e3895/67d7992fd01eb8fd6ac0c2a1_IMG_4731.png
description: Omise is a Singapore‑based payments platform that provides a simple, secure API for accepting online payments,
  managing recurring subscriptions, and handling payouts across multiple currencies. Founded in 2013, Omise serves merchants,
  developers, and enterprises in Southeast Asia and beyond, offering features such as fraud detection, tokenization, and comprehensive
  dashboard analytics. The company emphasizes developer‑friendly documentation, robust SDKs, and compliance with regional
  financial regulations.
url: https://raw.githubusercontent.com/api-evangelist/opn-ooo/refs/heads/main/apis.yml
x-type: company
x-source: harvest:vc-portfolio
x-tier: profiled
x-tier-reason: enrichment pass 2026-10-25 (modular-v1; was harvest)
specificationVersion: '0.20'
created: '2026-10-25'
modified: '2026-10-25'
tags:
- Company
- Payments
- API
- FinTech
- Southeast-Asia
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: SecurityTxt
  url: well-known/opn-ooo-status-security.txt
- type: WellKnown
  url: well-known/opn-ooo-well-known.yml
- type: Spectral
  url: rules/opn-ooo-rules.yml
- type: JSONLD
  url: json-ld/opn-ooo-context.jsonld
- type: Vocabulary
  url: vocabulary/opn-ooo-vocabulary.yml
- type: Webhooks
  url: asyncapi/opn-ooo-webhooks.yml
- type: DataModel
  url: data-model/opn-ooo-data-model.yml
- type: ChangeLog
  url: changelog/opn-ooo-changelog.yml
- type: Conventions
  url: conventions/opn-ooo-conventions.yml
- type: Authentication
  url: authentication/opn-ooo-authentication.yml
- type: Deprecation
  url: lifecycle/opn-ooo-lifecycle.yml
- type: Lifecycle
  url: lifecycle/opn-ooo-lifecycle.yml
- type: Conformance
  url: conformance/opn-ooo-conformance.yml
- type: Hosts
  url: hosts/opn-ooo-hosts.yml
- type: Vendors
  url: vendors/opn-ooo-vendors.yml
- type: TermsOfService
  url: https://docs.omise.co/terms
- type: StatusPage
  url: https://status.omise.co/
- type: SignUp
  url: https://dashboard.omise.co/v2/signup
- type: Pricing
  url: https://omise.co/en/pricing
- type: Newsroom
  url: https://omise.co/en/newsroom
- type: Blog
  url: https://omise.co/en/blog
- type: GettingStarted
  url: https://docs.omise.co/en/docs/international
- type: Documentation
  url: https://docs.omise.co/
- type: DomainSecurity
  url: security/opn-ooo-domain-security.yml
- type: Website
  url: https://omise.co
apis:
- aid: opn-ooo:opn-ooo-api
  name: Omise API
  description: 'Omise API as documented publicly: 31 operations. Contract generated from the documentation by API Evangelist
    (2026-10-25); not the provider''s own document.'
  humanURL: https://docs.omise.co/en/cards-api/international
  baseURL: https://api.omise.co
  properties:
  - type: OpenAPI
    url: openapi/_ae-authored/opn-ooo-openapi-generated.yml
    x-provenance: generated
  - type: JSONSchema
    url: json-schema/opn-ooo-post-charges-request-schema.json
  - type: JSONSchema
    url: json-schema/opn-ooo-post-charges-id-refunds-response-schema.json
  - type: JSONSchema
    url: json-schema/opn-ooo-patch-customers-id-cards-cardid-request-schema.json
  - type: JSONSchema
    url: json-schema/opn-ooo-get-tokens-id-response-schema.json
  - type: JSONSchema
    url: json-schema/opn-ooo-post-tokens-response-schema.json
  - type: JSONSchema
    url: json-schema/opn-ooo-get-forex-currency-response-schema.json
x-backed-by:
- 500-global
x-enrichment:
  date: '2026-10-25'
  status: enriched
  artifacts_added: 24
  pass: modular-v1
  engine: identity=local,contract=local,surfaces=local,docs=local,regulatory=local

Omise API — frequently asked questions

Does Omise have an API?

Yes. APIs.io lists 1 API from Omise, including Omise API.

Is there an OpenAPI specification for the Omise API?

Yes. APIs.io indexes 1 OpenAPI specification for Omise, each linked for download from this page.

How do I authenticate with the Omise API?

Omise uses bearer-token authentication (1 scheme). The details are profiled on APIs.io as Opn Ooo Authentication.

Is the Omise API ready for AI agents?

Omise has a Kin Score of 42.6 out of 100 (developing) and an Agent Readiness score of 19.8 (agent-aware), scored by API Evangelist on 2026-10-31.

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/opn-ooo"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/opn-ooo/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/opn-ooo/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.

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