For Agents
Find retirable carbon credits on Base with live USDC prices, quote a retirement, retire credits from a wallet or a signed x402 authorization, and fetch the Carbonmark certificate.
Use for: Find carbon credits from 2020 vintages priced under 20 USDC per tonne, Get a quote for retiring 1.5 tonnes of a specific carbon class, I want to retire carbon credits for my company's travel emissions, Retrieve the Carbonmark certificate for my retirement transaction
Not supported: Does not handle emissions calculation, fiat payments, wallet custody, or registry issuance of new credits. Use for discovering, quoting, retiring, and certifying tokenized carbon credits on Base only.
The x402 Carbon Retirement API lets a client find tokenized carbon credits on Base, price a retirement, and retire credits through Klima Protocol and the Carbonmark marketplace, then resolve the public Carbonmark certificate. Discovery returns pooled protocol supply as carbonClasses and fixed seller asks as marketplaceListings, each with USDC-per-tonne prices, liquidity, and project metadata, filterable by vintage, country, methodology, and price ceiling. A retirement can be sent from the caller's own wallet as an approve-then-retire call batch, or funded by a signed USDC or kVCM authorization that the service relays non-custodially. Discovery, quotes, and certificates are free; retiring costs the credit price plus a fee, and the top-supply snapshot is a paid x402 call.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the x402 Carbon Retirement API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcarbonmark.com%2Fcarbonmark" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcarbonmark.com%2Fcarbonmark" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with x402 Carbon Retirement API.
Browse retirable carbon supply on Base, filtered by vintage, country, methodology, project, or maxUsdcPricePerTonne
Quote the price, fee, and total for retiring a given amount of tonnes from one carbonClass, listingId, or credit
Build an unsigned approve-then-retire call batch for a caller's own wallet to submit
Generate EIP-712 typed data for a signed USDC or kVCM authorization and relay the retirement non-custodially
Resolve the public Carbonmark certificate for a confirmed retirement transaction by txHash
Read the machine-readable error-code registry with retryability and remedies for each error
Patterns agents use x402 Carbon Retirement API for, with concrete tasks.
★ AI agent offsetting a measured footprint
An AI agent that has calculated an emissions figure can act on it by retiring matching credits. Through Jentic the agent searches for 'retire carbon credits', reads supply from GET /api/discover, prices the chosen class with GET /api/quote, and then either builds a wallet batch or prepares a signed authorization for the user to approve. The retirement settles on Base and the agent returns the Carbonmark certificate link.
Call GET /api/discover with vintage 2020 and maxUsdcPricePerTonne '20', quote 2 tonnes of the cheapest carbonClass with GET /api/quote on chainId 8453 with the USDC inputToken, and present the total for approval
Wallet-submitted retirement
Teams that already operate a wallet on Base can keep custody and submit the transaction themselves. GET /api/prepare/retire returns an ordered approve and retire batch of unsigned calls plus the authoritative quote, built for a given chainId, inputToken, and amount. The call only builds the batch; nothing is broadcast until the wallet sends it.
Call GET /api/prepare/retire with chainId 8453, the USDC inputToken address, amount '1', and a carbonClass, then hand the returned unsigned batch to the user's wallet for signing
Relayed retirement from a signed authorization
When the payer should not send a transaction, GET /api/prepare-auth returns EIP-712 typedData and a ready-to-send actionsRetireRequest. After the payer signs the typed data, POST /api/actions/retire relays it, settles the retirement, and returns the certificate in one call. The request requires chainId, inputToken, amount, and from, and either a beneficiary address in details or beneficiaryIsPayer set to true.
Call GET /api/prepare-auth with chainId 8453, inputToken, amount '0.5', from set to the payer address, and beneficiaryIsPayer true, have the payer sign typedData, then POST the actionsRetireRequest to /api/actions/retire
Proof of retirement for sustainability reporting
Sustainability reports need verifiable proof that credits were retired. GET /api/certificate takes a txHash and returns one entry per retirement in that transaction, each with its public certificateUrl. The spec notes that a 404 immediately after confirmation means the subgraph has not indexed it yet, so a reporting job should retry.
Call GET /api/certificate with the retirement txHash, retry on 404 until indexed, and attach each certificateUrl to the quarterly report
12 endpoints — the x402 carbon retirement api lets a client find tokenized carbon credits on base, price a retirement, and retire credits through klima protocol and the carbonmark marketplace, then resolve the public carbonmark certificate.
METHOD
PATH
DESCRIPTION
/api/discover
List retirable carbon credits with live prices
/api/quote
Price a retirement
/api/prepare/retire
Build a wallet-submitted retirement batch
/api/prepare-auth
Build the authorization to sign
/api/actions/retire
Retire credits with a signed x402 authorization
/api/certificate
Resolve the Carbonmark certificate
/api/discover
List retirable carbon credits with live prices
/api/quote
Price a retirement
/api/prepare/retire
Build a wallet-submitted retirement batch
/api/prepare-auth
Build the authorization to sign
/api/actions/retire
Retire credits with a signed x402 authorization
/api/certificate
Resolve the Carbonmark certificate
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>What agents get from Jentic-routed access to this vendor.
Setup
Wiring this API by hand means sequencing discover, quote, and prepare calls, then handling an x402 402 challenge and an EIP-712 signature round-trip before POST /api/actions/retire settles. Through Jentic you install once, import it from the API Directory, and your agent calls each step with its input schema in hand.
Permission scoping
The API carries the carbon class, listing, and amount in query parameters or the request body, so rules bound which operations your agent may call, not which credits it touches. You choose the operations it may call, so paid ones like GET /api/prepare-auth and POST /api/actions/retire are not included unless you add them.
Credential isolation
This API needs no account or API key: paid actions are funded by a payer-signed authorization or a wallet transaction, and the signature happens outside the API call. For any API you add that does use a key, your own Jentic One instance keeps it encrypted and injects it at execution time so it never reaches the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'find carbon credits to retire' or 'get a carbon retirement certificate', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using x402 Carbon Retirement API through Jentic.
Does the x402 Carbon Retirement API require authentication?
The OpenAPI spec declares no API key or account scheme. Discovery, quotes, certificates, and the metadata routes are open, while paid actions are funded per call: GET /api/catalog is a $0.001 x402 payment, and a retirement is paid either by the caller's wallet sending the prepared batch or by a payer-signed USDC (EIP-3009) or kVCM (EIP-2612) authorization relayed through POST /api/actions/retire.
Can I see prices before retiring credits?
Yes. GET /api/discover lists carbonClasses and marketplaceListings with USDC-per-tonne prices and liquidity, and GET /api/quote returns the retirement price, fee, total, and a suggested maximum input for a specific amount of one carbonClass, listingId, or credit. Both are free per the spec.
What are the rate limits for the x402 Carbon Retirement API?
The OpenAPI spec does not specify rate limits. GET /api/errors returns every error code with its status and retryability, which is the best source for handling throttling or transient failures; see https://x402.klimalabs.com for service details.
Is there a Carbonmark MCP server?
You don't need an MCP server to give your agent the x402 Carbon Retirement API. Jentic connects it directly from the API Directory: import it and your agent calls the discover, quote, and certificate operations on demand, with paid actions settling per call and no key to manage.
Can I limit what my agent is allowed to do with this API?
Yes. For example, write a rule that allows only GET /api/discover, GET /api/quote, and GET /api/certificate, so the agent can research supply, price retirements, and fetch certificates, but cannot call GET /api/prepare-auth or POST /api/actions/retire to start a paid retirement. Every call it makes is logged.
How do I quote a carbon retirement through Jentic?
Add the x402 Carbon Retirement API to your Jentic One instance from the directory. Your agent searches for 'quote a carbon credit retirement', loads the quote operation, and calls GET /api/quote with chainId 8453, an inputToken address, an amount in tonnes, and one of carbonClass, listingId, or credit. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED