Africa Token Sale is Live! — Early access allocations for tokenized African real-world assets. Limited slots available.
Request Early Access Back to Home
Developer Documentation

Africore
Developer Docs.

Everything you need to integrate with the Africore Protocol — SDKs, APIs, chain specs, and node operator guides.

Version 2.0 Updated April 2026
Get Started API Reference →
Section 1
Quick Start

Africore is in closed beta. Access requires an approved developer account. Apply at africore.io/request-access.

Follow these steps to make your first call to the Africore API.

1
Request developer access and receive your API key at africore.io/request-access. Approved accounts receive credentials within 2 business days.
2
Install the SDK: npm install @africore/sdk
3
Initialize the client with your key and call your first asset fetch using the example below.
import { AfricoreClient } from '@africore/sdk';

const client = new AfricoreClient({
  apiKey: 'YOUR_API_KEY',
  network: 'mainnet'
});

// Fetch all tokenized assets
const assets = await client.assets.list({ limit: 10 });
console.log(assets);
Section 2
Architecture Overview

Africore is a modular 4-layer protocol. Each layer is independently upgradeable through governance, allowing the protocol to evolve without disrupting the underlying asset infrastructure.

Chain Layer
EVM settlement — the base layer for all asset transactions and on-chain state.
Registry Layer
On-chain title and metadata — the authoritative source for every tokenized asset.
Bridge Layer
Cross-chain routing — moves RWA tokens across supported networks without wrapping.
Oracle Layer
Decentralised price feeds — licensed node operators provide signed, on-chain valuations.
Section 3
Africore Chain

Africore Chain is an EVM-compatible Layer 1 purpose-built for real-world asset settlement. It delivers 3-second block finality and sub-cent gas fees while enforcing the ERC-3643 permissioned token standard at the base layer — ensuring every on-chain transfer is compliant by default.

ParameterValue
Block Time3 seconds
ConsensusDelegated Proof of Stake (DPoS)
CompatibilityEVM / Solidity
Token StandardERC-3643
Native TokenAFRI
GasAFRI or USDC
Section 4
Asset Registry API

The Asset Registry is the on-chain source of truth for all tokenized assets on the Africore Protocol. Every registry entry contains legal ownership data, jurisdiction metadata, full valuation history, yield schedule, compliance status, and the token contract address. The registry is publicly queryable — no API key required for read operations.

GET https://api.africore.io/v1/assets/afr_ke_farm_0041

{
  "asset_id": "afr_ke_farm_0041",
  "name": "Rift Valley Farmland Block C",
  "jurisdiction": "KE",
  "category": "agriculture",
  "valuation_usd": 2400000,
  "yield_rate_pct": 8.4,
  "compliance_status": "verified",
  "token_address": "0x4f2c...8a1d"
}
Section 5
Africore Bridge

The Africore Bridge enables tokenized RWAs to move across chains without wrapping. Unlike conventional bridge architectures that wrap tokens into synthetic representations, the Africore Bridge transfers native compliance data alongside the asset token — preserving KYC/AML enforcement on every destination chain.

The following networks are currently supported or planned:

Africore ChainNative
Ethereum MainnetLive
Polygon PoSLive
BNB Smart ChainLive
Arbitrum OneLive
BaseComing Soon
Section 6
Oracle Network

The Africore Oracle Network provides decentralised price feeds for all tokenized real-world assets on the protocol. Feeds are operated by licensed node holders — each of whom stakes AFRI as collateral against bad or manipulated reporting. Slashing conditions are enforced automatically on-chain.

Update frequency varies by asset class, reflecting the liquidity and volatility characteristics of each category:

Asset ClassUpdate Frequency
Agricultural AssetsEvery 6 hours
Real EstateEvery 24 hours
InfrastructureEvery 7 days
Energy / SolarEvery 1 hour
Section 7
Node Operator Guide

Running an Africore node requires a valid node licence NFT (available at node-sale.html), a qualified server meeting minimum hardware specifications, and a funded AFRI staking wallet. Node operators earn protocol fee rewards and oracle submission rewards proportional to their stake and uptime.

Minimum server specifications:

CPU8 cores
RAM32 GB
Storage2 TB NVMe
Network1 Gbps
OSUbuntu 22.04

Setup steps:

1

Purchase your node licence NFT at node-sale.html. Licences are tiered and grant varying reward multipliers.

2

Download the node client from the developer portal after your developer account is approved.

3

Configure node.yaml with your licence NFT address and preferred RPC endpoints.

4

Fund your node wallet with a minimum of 5,000 AFRI staking collateral.

5

Start the node and verify sync against the network explorer. Sync typically completes within 15–30 minutes from genesis.

Section 8
SDKs & Tools

Official Africore SDKs are available for the most common languages. Community-maintained libraries for additional languages are listed in the developer portal.

LanguagePackageVersionStatus
JavaScript / TypeScript@africore/sdkv1.2.0Stable
Pythonafricore-pyv0.9.1Beta
Goafricore-gov0.7.0Beta
Rustafricore-rsComing Soon
Section 9
Error Reference

All Africore API errors are returned in a standard envelope format. Parse the error.code field to handle errors programmatically.

{
  "success": false,
  "error": {
    "code": "ERR_AUTH_INVALID",
    "message": "The provided API key is invalid or has been revoked.",
    "status": 401
  }
}
Error CodeDescription
ERR_AUTH_INVALIDThe API key is missing, malformed, or has been revoked.
ERR_ASSET_NOT_FOUNDNo asset exists for the given asset ID in the registry.
ERR_COMPLIANCE_FAILThe requesting wallet has not completed required KYC/AML verification.
ERR_JURISDICTION_BLOCKEDThe operation is not permitted in the user's detected jurisdiction.
ERR_RATE_LIMITToo many requests. Default limit is 100 requests per minute per API key.

Ready to start
building?