Developer & API

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

CSCS data: status not confirmed

Current production data, higher limits and wider scopes come with the CSCS data licence.

Credits & billing

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

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.

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

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

Tool	Description	Cost

Local MCP server

Download MCP server

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

Claude Desktop config (claude_desktop_config.json). CSCS_MCP_BASE is required — it is this deployment's address.

{
  "mcpServers": {
    "cscs-marketsphere": {
      "command": "python",
      "args": ["/path/to/mcp_server.py"],
      "env": {
        "CSCS_MCP_API_KEY": "cscs_sk_sandbox_XXXXXXXXXXXXXXXX",
        "CSCS_MCP_BASE": "https://<this-marketsphere-deployment>"
      }
    }
  }
}

Connect your AI agent

Remote MCP

Add this server to your agent's MCP config (streamable HTTP). It authenticates with your API key (the same X-API-Key issued above), with the same plan scopes, rate limits and credits as the REST API.

{
  "mcpServers": {
    "cscs-marketsphere": {
      "type": "http",
      "url": "https://<this-marketsphere-deployment>/mcp",
      "headers": {
        "X-API-Key": "cscs_sk_sandbox_XXXXXXXXXXXXXXXX"
      }
    }
  }
}

Every tool call is metered to your key's account; investor identity is always masked, and a failed call comes back as a tool error, never as data.

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.

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

Webhooks

Push events to your endpoint as they happen. Register, test and verify deliveries with an HMAC-SHA256 signature.

Webhooks push an event to your endpoint when a KYC decision is made on your account; your credit balance falls below the low-balance threshold. Sign in to register and manage them.

Your invoice is computed from real metered usage. Usage-based charging is not switched on, so it is not charged.

Python SDK

marketsphere.py

Download Python SDK

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

# 1. Download the SDK (button above) into your project
#    It uses the Python standard library only: there is nothing to install.

# 2. Use it
from marketsphere import MarketSphere

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

API reference

Open interactive API explorer

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

GET	`/api/v1/meta` Key check: your plan, scopes, rate limit, AI daily cap, credits left and the endpoints you can call.	CSCS data
GET	`/api/v1/securities` Security master — priced/active instruments.	CSCS data
GET	`/api/v1/prices` Latest price list (open/close/change) per instrument.	CSCS data
GET	`/api/v1/symbols` Symbol directory: each security's code and name, from the securities master.	CSCS data
GET	`/api/v1/trades` Trade-activity aggregates: totals and concentration by dealing member (not individual trades).	CSCS data

Full request/response schemas live in the OpenAPI spec and the live Swagger UI at /api/v1/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

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

Packaged Python client (not yet published)

planned

JS SDK

Packaged JavaScript client (not yet published)

planned

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