Karak
Karak — now operating as OpenGDP — is a blockchain infrastructure project incubated by Andalusia Labs and backed by Pantera Capital. Originally a universal restaking protocol (K2 / v1 + v2 staking), it has rebranded to OpenGDP, positioned as a global base layer for programmable GDP: an EVM-compatible execution layer unifying stablecoin settlement, real-world asset tokenization, and autonomous economic workflow orchestration for enterprises, institutions, and governments. The stack spans the OpenGDP Network (base execution layer with adaptive multi-proposers, automatic fee swaps, dedicated blockspace, native orderbook, private transactions, and stablecoin gas), the OpenGDP Network Stack (ONS) for launching bespoke economic networks, and a platform layer for moving value, programming assets, and orchestrating GDP. It exposes on-chain/EVM infrastructure (precompiles, validators, the K2 bridge) rather than a hosted REST API; developer resources are published at docs.opengdp.network.
Karak is profiled on the APIs.io network. Tagged areas include Company, Cryptocurrency, Blockchain, Restaking, and Stablecoins.
Karak’s developer surface includes documentation, getting-started guide, engineering blog, and 8 more developer resources.
Kin Score
Markets this provider is in provisional
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.
| Market | Position | Depth | Registered MCP server | Declares compatibility |
|---|---|---|---|---|
| Stablecoins and Tokenization (stablecoin issuers, tokenized assets) | undeclared | - | - | - |
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.
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
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
Access & Security 3
Authentication, authorization, and security posture
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Source (apis.yml)
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.