# Yabie

**Canonical:** https://apis.io/providers/yabie/  
**Website:** https://yabie.com/  
**APIs profiled:** 1

Yabie is a technology company focused on providing innovative solutions in the digital marketplace. It aims to connect businesses with advanced API-driven services, enhancing integration capabilities and streamlining workflows across various industries. The company emphasizes scalability, security, and developer-friendly tools to foster ecosystem growth and enable seamless data exchange.

## Kin Score — 13.9 / 100 (emerging)

Scored 2026-11-06 under rubric 0.27.0. Trend: flat (-4.1 from 18.0).

| Facet | Score |
|---|---|
| Discoverability | 55.4 |
| Contract Quality | 0.0 |
| Contract Governance | 0.0 |
| Operational Transparency | 34.2 |
| Developer Ergonomics | 8.3 |
| Access Clarity | 13.2 |

Regulatory layer — **Horizontal (data, software, accessibility, platform)**: 12.7 (matched via fallback).

## Agent readiness — 2.9 (human-only)

| Dimension | Value |
|---|---|
| Spec Presence | no |
| Agentic Access | no |
| Reversibility Documented | no |
| MCP Server | no |
| Auth Clarity | no |
| Idempotency | no |
| Error Semantics | no |
| OpenAPI Examples | no |
| Rate Limit Signal | no |
| Event Surface Described | no |
| Agent Skills | no |
| Well Known Catalog | yes |
| Consent Identity | no |
| Agent Card | no |
| Dry Run Mode | no |
| Delegated Identity | no |
| Protected Resource Metadata | no |
| Dynamic Client Registration | no |
| Agentic Commerce | no |
| Pagination Ratio | na |
| Operation Distinctiveness | na |
| MCP Tool Quality | na |

## Access

Unknown — onboarding: unknown, pricing: unknown, trial: no (confidence: low).

## APIs (1)

- **Yabie API** — Yabie's API documentation is hosted on their support site covering product integration.

## Security (2)

- **Yabie Domain Security** — DMARC
- **Yabie Trust Center** — trust center published

## Tags

Company

---

Profiled by [API Evangelist](https://apievangelist.com) and published on [APIs.io](https://apis.io/providers/yabie/). Scores are computed from the provider's own public artifacts under a published rubric.