BALAD CORP
BALAD CORP (Balad) is a Cairo-based fintech providing cross-border payout and inward-remittance infrastructure for Egypt. Its Balad Gateway APIs let money transfer operators (MTOs), RemTechs, and superapps pay out to Egyptian beneficiaries via bank transfer to CBE-licensed banks over IPN, mobile wallets, and cash pickup at agent locations nationwide. The REST APIs are secured with OAuth 2.0 client credentials and cover exchange rates, balances, secrets management, lookups, transaction creation, status tracking, reconciliation, and HMAC-signed status webhooks, with a full sandbox for testing. Balad is backed by 500 Global, Acasia Ventures, First Circle Capital, Future Africa, and Launch Africa Ventures.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles BALAD CORP the way a machine reads it — 12 machine-readable artifacts across 7 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — BALAD CORP scores 43.8/100 (thin), with a separate agent-readiness read of 69/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile BALAD CORP
Each block below is one kind of artifact we hold for BALAD CORP. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 7
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
BALAD CORP APIs/Authentication API
The APIs/Authentication API from BALAD CORP — 1 operation(s) for apis/authentication.
BALAD CORP APIs/Core/Balance API
The APIs/Core/Balance API from BALAD CORP — 1 operation(s) for apis/core/balance.
BALAD CORP APIs/Core/Exchange rate API
The APIs/Core/Exchange rate API from BALAD CORP — 1 operation(s) for apis/core/exchange rate.
BALAD CORP APIs/Core/Secrets API
The APIs/Core/Secrets API from BALAD CORP — 2 operation(s) for apis/core/secrets.
BALAD CORP APIs/Link/Lookups API
The APIs/Link/Lookups API from BALAD CORP — 4 operation(s) for apis/link/lookups.
BALAD CORP APIs/Link/Reconciliation API
The APIs/Link/Reconciliation API from BALAD CORP — 1 operation(s) for apis/link/reconciliation.
BALAD CORP APIs/Link/Transactions API
The APIs/Link/Transactions API from BALAD CORP — 7 operation(s) for apis/link/transactions.
Scroll within the panel for all 7 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
balad-corp-mcp.yml
MCP SERVEREvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Balad Gateway Webhooks
Event-driven webhook surface for the Balad Gateway. Balad POSTs signed event envelopes to a partner-registered, whitelisted webhook URL when a transaction changes status. Genera...
ASYNCAPISecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Resources
Every other property we hold for BALAD CORP — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 4
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Company 1
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/balad-corp · machine-readable index on apis.io