Skip to main content
The cNGN API skill packages this documentation into a form coding agents can load directly. Install it once, and your agent writes cNGN integrations that encrypt payloads correctly, resolve network IDs per environment, and handle money-moving endpoints safely, without you pasting the rules into every prompt.

wrappedcbdc/cNGN_api_skill

Source repository for the skill.
The skill teaches an agent how the API behaves. It is not a runtime dependency and it does not replace the official SDKs, which do the actual encryption work in your application.

Why agents need it

Three parts of this API are easy to get wrong from general knowledge alone, and the skill front-loads all three:
POST and PUT bodies must be AES-256-CBC encrypted into {content, iv}, and the data field of every success response is encrypted to your Ed25519 public key. An agent working from REST conventions alone sends plain JSON and gets 400 Missing encryption data, key, or IV. See Encryption.
networkId is a database identifier that differs between test and live. Agents like to hard-code identifiers they have seen once. The skill requires resolving them at runtime from Get Networks and skipping networks where isDisabled is true. See Networks.
A timeout on Redeem Asset, Withdraw, or Bridge does not mean the request was not processed. The skill requires confirming state with Verify Withdrawal or Get Transactions before any retry. See Error Reference.

What it covers

Install for Claude Code

1

Add the marketplace

2

Install the plugin

3

Start building

The skill activates on its own when a task mentions cNGN, cngn_test or cngn_live keys, or Naira stablecoin payouts. Invoke it explicitly with /cngn-api.

Use with other agents

Every file in the skill is plain Markdown with no tool-specific syntax, so any agent can read it.
These read AGENTS.md from your repository root. Clone the skill into your project, or copy AGENTS.md and the skills/cngn-api/ directory into it:

Verifying your keys

The skill ships a helper that exercises both encryption directions locally, which is the fastest way to tell a key problem from an API problem:
Passing - as the key reads CNGN_ENCRYPTION_KEY from the environment, so the secret stays out of your shell history.
Generate your Ed25519 key pair without a passphrase (ssh-keygen -t ed25519 -f cngn_api_key -N ""). A passphrase encrypts the private section of the file, and the decryption implementations then fail with Unable to find Ed25519 key data. Protect the file with filesystem permissions and a secrets manager instead. See Generating SSH Keys.
Never let an agent write an API key, encryption key, or Ed25519 private key into source control, a client-side bundle, or a mobile app. All cNGN credentials are server-side only.

Staying current

The skill is generated from this documentation site, which is in turn documented from the cNGN API itself. When an endpoint changes here, the matching reference file and the OpenAPI description in the skill repository are updated and its version is bumped. Re-run /plugin marketplace update cngn-skills in Claude Code, or pull the repository, to pick up changes.