Developer & API

Build on the depository's own market-intelligence data.

Sandbox · anonymised CSCS data

Production data + higher limits & scopes activate with the CSCS data licence.

Credits & billing

One balance meters REST, AI and MCP calls the same way.

Sign in to view your credits balance

Credits are metered per organisation. Sign in to see your balance, usage and buy more.

API keys

Issue, list and revoke sandbox keys scoped to your organisation.

Sign in to issue a sandbox key

Developer keys are scoped to your organisation. Sign in to the MarketSphere app, then return here to issue and manage sandbox keys.

Quickstart

Call GET /api/v1/securities with your key in the X-API-Key header.

curl -sS https://marketsphere.cscs.ng/api/v1/securities \
  -H "X-API-Key: cscs_sk_sandbox_XXXXXXXXXXXXXXXX"

Replace the placeholder with a sandbox key issued above. Public API access is sandbox-only and read-only.

MCP — AI-agent access

manifest · live

Expose CSCS tools to any AI agent over the Model Context Protocol — metered on the same credits balance.

Any AI agent (Claude Desktop, copilots, autonomous workflows) can call CSCS tools over the Model Context Protocol. Each tool call debits credits from the same balance as REST and AI. The manifest below is live — it advertises the exact tools and their credit cost.

Tool catalogue
ToolDescriptionCost
Local MCP server
Download MCP server

A runnable local stdio MCP server for Claude Desktop — auth via your API key, metered per tool-call.

Connect your AI agent
Remote MCP transport: planned — tools listed today

Add this server to your agent's MCP config. It authenticates with your sandbox API key (the same X-API-Key issued above).

{
  "mcpServers": {
    "cscs-marketsphere": {
      "url": "https://marketsphere.cscs.ng/mcp",
      "transport": "http",
      "headers": {
        "X-API-Key": "cscs_sk_sandbox_XXXXXXXXXXXXXXXX"
      }
    }
  }
}

The remote MCP endpoint URL is a placeholder — remote transport is planned. The tool manifest above is live today so agents can be built against the exact contract.

API Access & Entitlements

Your subscription tier (RBAC) decides which endpoint scopes (data / ai / intel) your keys can call — plus rate limit, AI daily cap and credits.

Sign in to see what your tier unlocks

API access follows your subscription tier (RBAC) — your org's plan decides which endpoint scopes (data / ai / intel) your keys can call.

Webhooks

Push real-time events to your endpoint. Register, test and verify deliveries with an HMAC-SHA256 signature.

Sign in to register webhooks

Webhooks push real-time events (price ticks, ownership alerts, settlement) to your endpoint. Sign in to register and manage them.

Sign in to view your invoice

Your invoice is computed from real metered usage — illustrative, not charged, in sandbox.

Python SDK

marketsphere.py · live
Download Python SDK

A single-file client (marketsphere.py) that wraps the sandbox REST API with your X-API-Key.

# 1. Download the SDK (button above) into your project
# 2. Install its one dependency
pip install requests

# 3. Use it
from marketsphere import MarketSphere

ms = MarketSphere(api_key="cscs_sk_sandbox_XXXX")
print(ms.securities())
print(ms.prices())

Machine-to-machine REST API. All endpoints require the X-API-Key header and serve anonymised CSCS sandbox data.

GET/api/v1/meta

Sandbox metadata: exchange, environment, rate limits.

sandbox
GET/api/v1/securities

Security master — priced/active instruments.

sandbox
GET/api/v1/prices

Latest price list (open/close/change) per instrument.

sandbox
GET/api/v1/symbols

Symbol directory with class/status metadata.

sandbox
GET/api/v1/trades

Anonymised trade activity records.

sandbox
GET/api/v1/ownership-summary

Aggregated beneficial-ownership concentration.

sandbox

Full request/response schemas live in the OpenAPI spec and the live Swagger UI at /docs.

White-label

Brand your MarketSphere instance — branding + org-scoped data provision on shared infrastructure. Dedicated-tenant isolation + live DNS are the enterprise infra step.

White-label provisioning

Provisions your branding + org-scoped data on shared infrastructure — live today.

Dedicated isolation + live DNS — enterprise infra step

Sign in to provision white-label branding

White-label config is scoped to your organisation. Sign in to the MarketSphere app, then return here to brand your instance.

Future concept — previews

The cards below are non-functional design concepts (note the amber Future concept chips and disabled controls). They preview where the platform is headed — none of these controls are live.

SDKs (Python / JS)

Future concept
Python SDK
pip install cscs-marketsphere
planned
JS SDK
npm i @cscs/marketsphere
planned

Illustrative only — official SDKs ship with the production platform. Until then, call the REST API directly (see Quickstart) or connect an MCP agent.