Onymos is a Menlo Park, California software company that sells "Features-as-a-Service" (FaaS) — pre-built, pro-code application components that enterprise engineering teams drop into their own web, mobile and IoT apps instead of building commodity functionality from scratch. The catalog spans Access (social/OAuth 2.0 login), Biometrics, Chat, Contacts, DataStore, DeepLink, Location/geofencing, Media, Notification, Payments, Share, and a document-intelligence family — DocEnhance (image enhancement and OCR pre-processing), DocID (client-side document classification) and DocKnow (intelligent document processing). Onymos is built on a "No-Data Architecture": the software runs inside the customer's own cloud or on-premises environment and Onymos never stores, sees, or accesses customer data, and customers may license the source code outright. Developers consume the features through JavaScript/TypeScript SDK objects (OnymosAccess, OnymosChat, OnymosUtil, OnymosPayment, OnymosDocID and siblings) across React, Angular, Ionic, Cordova, React Native, Flutter, Swift, Kotlin, Java, Python and Go. DocEnhance additionally exposes a documented asynchronous REST surface. Onymos states it is SOC 2 certified and HIPAA compliant, and it concentrates on healthcare, life sciences and laboratory workflows.
Onymos is listed with 1 API on the APIs.io network. Tagged areas include Features as a Service, SDK, Application Development, Mobile, and Document Processing.
Onymos’ developer surface includes API reference, documentation, support, engineering blog, authentication, and 15 more developer resources.
Regulatory Posture applies to this provider. Its tags matched the
Health 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/onymos/"><img src="https://apis.io/badge/onymos/card.svg" alt="Onymos 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):
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)
Stable Error Semantics+8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card+8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
11 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
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.
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.
Asynchronous document-image enhancement REST API. POST /api/enhance accepts a base64-encoded image plus a preset (document, auto-crop, photo or watermark) and returns a result_u...
aid: onymos
name: Onymos
description: 'Onymos is a Menlo Park, California software company that sells "Features-as-a-Service" (FaaS) — pre-built, pro-code
application components that enterprise engineering teams drop into their own web, mobile and IoT apps instead of building
commodity functionality from scratch. The catalog spans Access (social/OAuth 2.0 login), Biometrics, Chat, Contacts, DataStore,
DeepLink, Location/geofencing, Media, Notification, Payments, Share, and a document-intelligence family — DocEnhance (image
enhancement and OCR pre-processing), DocID (client-side document classification) and DocKnow (intelligent document processing).
Onymos is built on a "No-Data Architecture": the software runs inside the customer''s own cloud or on-premises environment
and Onymos never stores, sees, or accesses customer data, and customers may license the source code outright. Developers
consume the features through JavaScript/TypeScript SDK objects (OnymosAccess, OnymosChat, OnymosUtil, OnymosPayment, OnymosDocID
and siblings) across React, Angular, Ionic, Cordova, React Native, Flutter, Swift, Kotlin, Java, Python and Go. DocEnhance
additionally exposes a documented asynchronous REST surface. Onymos states it is SOC 2 certified and HIPAA compliant, and
it concentrates on healthcare, life sciences and laboratory workflows.'
url: https://raw.githubusercontent.com/api-evangelist/onymos/refs/heads/main/apis.yml
deliveryModel:
model: saas
open_source: false
commercial: true
callable_host: false
label: Hosted service · you call their endpoint
confidence: medium
source:
- pricing
generated: '2026-08-28'
method: derived
accessModel:
pricing: unknown
onboarding: approval
trial: false
try_now: false
public: false
label: Requires approval
confidence: medium
source:
- plans
- authentication
- rate-limits
- security
generated: '2026-11-06'
method: derived
image: https://onymos.com/wp-content/uploads/2021/05/onymos-social.jpg
x-type: company
x-source: harvest:secondary-market
x-tier: profiled
x-tier-reason: enrichment:local-v1
specificationVersion: '0.20'
created: '2026-08-26'
modified: '2026-08-26'
tags:
- Features as a Service
- SDK
- Application Development
- Mobile
- Document Processing
- Intelligent Document Processing
- OCR
- Healthcare
- Life Sciences
- Authentication
- Chat
- Push Notifications
- Geolocation
- Payments
- IoT
- No-Data Architecture
- Components
apis:
- name: Onymos DocEnhance API
description: Asynchronous document-image enhancement REST API. POST /api/enhance accepts a base64-encoded image plus a preset
(document, auto-crop, photo or watermark) and returns a result_url immediately; GET /api/enhance/results/{UUID} collects
the enhanced image as a base64 data URI. Presets remove shadows, wrinkles, speckle noise and non-solid watermarks, auto-crop
and deskew, and convert to black and white to raise OCR accuracy and human-in-the-loop verification. Requests are authorised
with an onymosIesAuthToken request header. This is the only network API Onymos documents publicly; every other Onymos
Feature is consumed as an in-process SDK object.
humanURL: https://onymos.com/api/onymos-docenhance-endpoints/
x-baseURL-status: not-published
x-baseURL-note: 'Onymos does not state a base host anywhere in the DocEnhance endpoint reference. The only host evidence
available is indirect and unusable as a base: the published example result_url is the path "/ies/api/enhance/results/{UUID}"
(note the /ies prefix the reference never explains), and api.onymos.com resolves via CNAME to onymosapiloadbalancer-154243126.us-west-2.elb.amazonaws.com
but returned HTTP 503 with an empty body on every path probed on 2026-08-26, including /ies/api/enhance. Recording baseURL
as missing rather than guessing api.onymos.com from the domain, per the enrichment contract.'
tags:
- Document Processing
- Image Enhancement
- OCR
- Intelligent Document Processing
- Asynchronous
properties:
- type: APIReference
url: https://onymos.com/api/onymos-docenhance-endpoints/
- type: Authentication
url: authentication/onymos-authentication.yml
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
- FN: APIs.json
email: info@apis.io
common:
- type: Website
url: https://onymos.com/
- type: APIReference
url: https://onymos.com/api/onymos-docenhance-endpoints/
- type: Documentation
url: https://onymos.com/api/onymos-access-functions/
name: Onymos Feature reference (Access)
- type: Support
url: https://onymos.com/contact-us/
- type: Blog
url: https://onymos.com/blog/
- type: BlogRSS
url: https://onymos.com/blog/feed/
- type: TermsOfService
url: https://onymos.com/terms-of-service/
- type: PrivacyPolicy
url: https://onymos.com/privacy-policy/
- type: Compliance
url: https://onymos.com/security/
name: SOC 2 certified and HIPAA compliant
- type: Packages
url: packages/onymos-packages.yml
- type: Authentication
url: authentication/onymos-authentication.yml
- type: Conventions
url: conventions/onymos-conventions.yml
- type: Conformance
url: conformance/onymos-conformance.yml
- type: Components
url: components/onymos-components.yml
- type: Lifecycle
url: lifecycle/onymos-lifecycle.yml
- type: Plans
url: plans/onymos-plans-pricing.yml
- type: RateLimits
url: rate-limits/onymos-rate-limits.yml
- type: LLMsTxt
url: llms/onymos-llms.txt
- type: TrustCenter
url: security/onymos-trust-center.yml
- type: DomainSecurity
url: security/onymos-domain-security.yml
x-enrichment:
date: '2026-08-26'
status: enriched
artifacts_added: 13
pass: local-v1
Onymos API — frequently asked questions
Does Onymos have an API?
Yes. APIs.io lists 1 API from Onymos, including Onymos DocEnhance API.
How do I authenticate with the Onymos API?
Onymos uses bearer-token authentication (apiKey · 1 scheme). The details are profiled on APIs.io as Onymos Authentication.
Is the Onymos API ready for AI agents?
Onymos has a Kin Score of 24.8 out of 100 (emerging) and an Agent Readiness score of 5.0 (human-only), scored by API Evangelist on 2026-11-06.
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.