# Takenos

**Canonical:** https://apis.io/providers/takenos/  
**Website:** https://takenos.com  
**APIs profiled:** 0

Takenos is a Latin American fintech offering a digital dollar wallet built for freelancers, remote workers, and businesses who need to receive cross-border payments. It lets users get paid from abroad, hold and save in digital dollars with daily yield, and spend via international (TakeCard) and local (SpicyCard) debit cards plus QR payments. Riding the LATAM stablecoin and onchain-finance wave, it targets remittance friction and local-currency inflation across markets including Argentina and Bolivia. Backed by a $5M seed round (investors include 500 Global). No public developer API is documented; this profile was enriched from public sources.

## Kin Score — 2.5 / 100 (minimal)

Scored 2026-08-20 under rubric 0.12.0. Trend: flat (+0.0 from 2.5).

| Facet | Score |
|---|---|
| Discoverability | 50.0 |
| Contract Quality | 0.0 |
| Governance | 0.0 |
| Contract Governance | 0.0 |
| Operational Transparency | 0.0 |
| Developer Ergonomics | 4.8 |
| Commercial Clarity | 0.0 |
| Access Clarity | 0.0 |

Regulatory layer — **Payments**: 9.4 (matched via tags).

## Agent readiness — 0.0 (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 | no |
| Consent Identity | no |
| Agent Card | no |
| Dry Run Mode | no |

## Access

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

## Security (1)

- **Takenos Domain Security** — TLSv1.3 · HSTS · DNSSEC · DMARC

## Tags

Company, Fintech, Payments, Digital Wallet, Cross-Border Payments, Remittances, Stablecoins, Latin America

---

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