timzinin-com Voyage Carbon Compliance Evidence API
The Voyage Carbon Compliance Evidence API from timzinin-com — 1 operation(s) for voyage carbon compliance evidence.
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/timzinin-com:timzinin-com-voyage-carbon-compliance-evidence-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: Zinin M2M Hub Voyage Carbon Compliance Evidence API
description: Pay-per-call data & tool APIs
version: 1.0.0
x-guidance: 'Zinin M2M Hub — pay-per-call data & tool APIs for AI agents. Each POST /api/{slug} operation below is a distinct paid tool: call GET /api/{slug}/schema first for the exact input shape, then POST with a signed PAYMENT-SIGNATURE header (x402 v2, USDC — see x-payment-info per operation) or omit it to receive a 402 with full payment requirements in the PAYMENT-REQUIRED header. The same catalog is also available as MCP JSON-RPC tool bundles at POST /mcp/{bundle} — see GET /.well-known/x402 for the list of bundles.'
tags:
- name: Voyage Carbon Compliance Evidence
paths:
/api/voyage-carbon-compliance-evidence:
post:
summary: EU ETS Voyage Carbon Exposure Evidence
description: Calculate deterministic EU ETS voyage exposure from buyer-supplied vessel, route, and fuel facts using pinned official fixtures. Get gas, fuel, segment, truth-ledger, confidence, limitation, and receipt evidence without provider calls or an automatic legal decision.
operationId: call_voyage_carbon_compliance_evidence
x-payment-info:
price:
mode: fixed
currency: USD
amount: '0.020000'
protocols:
- x402: {}
network: eip155:8453
payTo: '0x409D32aD39C02BC9B23a8b2d447532ed801b12dE'
asset: '0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913'
requestBody:
required: true
content:
application/json:
schema:
title: EU ETS voyage carbon exposure input
description: Apify UI projection of the authoritative two-mode contract. The platform schema cannot express nullable JSON fields, so the exact public Task and all cross-field/null rules are enforced by contract/input.schema.json and runtime validation.
type: object
additionalProperties: true
required:
- schemaVersion
- mode
- requestId
- portCalls
- legs
- berthRecords
properties:
schemaVersion:
type: string
title: schemaVersion
description: Contract version for validation and output interpretation. Enter `1.1.0`; other values are rejected before any Dataset delivery.
editor: textfield
mode:
type: string
enum:
- decision
- synthetic_demo
title: mode
description: Choose `decision` for buyer-supplied voyage facts or `synthetic_demo` for the fixed no-charge example. Runtime enforces the fields allowed in each mode.
editor: select
requestId:
type: string
maxLength: 64
title: requestId
description: Buyer correlation ID copied into the evidence receipt. Decision mode requires `rq_` plus 32 lowercase hexadecimal characters; demo mode uses `public-demo-v1`.
editor: textfield
portCalls:
type: array
minItems: 2
maxItems: 9
items:
type: object
additionalProperties: false
required:
- portCallId
- unlocode
- memberStatePort
- isPortOfCall
- specialTreatment
- startedAt
- endedAt
properties:
portCallId:
type: string
pattern: ^[A-Za-z0-9][A-Za-z0-9._:-]{0,63}$
title: portCallId
description: Unique port-call identifier used by legs and berth records. Use 1–64 letters, digits, dots, underscores, colons, or hyphens, beginning with a letter or digit.
editor: textfield
unlocode:
type: string
pattern: ^[A-Z0-9]{5}$
title: unlocode
description: Five-character uppercase UN/LOCODE for the observed port, such as `NLRTM` or `USNYC`. It supports route-scope and evidence interpretation.
editor: textfield
memberStatePort:
type: boolean
title: memberStatePort
description: Set true only when the supplied port fact is a qualifying EU ETS Member State port; this flag affects the voyage-scope calculation.
editor: checkbox
isPortOfCall:
type: boolean
title: isPortOfCall
description: Set true when this stop qualifies as a port of call under the buyer's evidence. False keeps the stop visible while excluding it from ordinary port-call treatment.
editor: checkbox
specialTreatment:
type: string
enum:
- ordinary
- excluded_stop
- neighbouring_container_transhipment
- unknown
title: specialTreatment
description: 'Regulatory treatment asserted for this stop: ordinary, excluded stop, neighbouring container transhipment, or unknown. Unknown produces a review gap rather than silent certainty.'
editor: select
startedAt:
type: string
pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}Z$
title: startedAt
description: UTC start of the port-call interval in exact `YYYY-MM-DDTHH:mm:ssZ` form. It must precede the matching end time and align with linked activity.
editor: textfield
endedAt:
type: string
pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}Z$
title: endedAt
description: UTC end of the port-call interval in exact `YYYY-MM-DDTHH:mm:ssZ` form. It bounds berth activity and voyage chronology checks.
editor: textfield
title: portCalls
description: Ordered array of 2–9 buyer-supplied port-call facts. IDs must be unique and are referenced by voyage legs and optional berth-consumption records.
editor: json
legs:
type: array
minItems: 1
maxItems: 8
items:
type: object
additionalProperties: false
required:
- legId
- departurePortCallId
- arrivalPortCallId
- departureAt
- arrivalAt
- fuelRecords
properties:
legId:
type: string
pattern: ^[A-Za-z0-9][A-Za-z0-9._:-]{0,63}$
title: legId
description: Unique voyage-leg identifier used in the evidence ledger. Use 1–64 letters, digits, dots, underscores, colons, or hyphens, beginning with a letter or digit.
editor: textfield
departurePortCallId:
type: string
pattern: ^[A-Za-z0-9][A-Za-z0-9._:-]{0,63}$
title: departurePortCallId
description: Exact `portCallId` of this leg's departure stop. The referenced port call must exist in `portCalls` and precede the arrival stop.
editor: textfield
arrivalPortCallId:
type: string
pattern: ^[A-Za-z0-9][A-Za-z0-9._:-]{0,63}$
title: arrivalPortCallId
description: Exact `portCallId` of this leg's arrival stop. The referenced port call must exist in `portCalls` and follow the departure stop.
editor: textfield
departureAt:
type: string
pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}Z$
title: departureAt
description: UTC departure timestamp in exact `YYYY-MM-DDTHH:mm:ssZ` form. Runtime checks it against the linked port calls and fuel-consumption intervals.
editor: textfield
arrivalAt:
type: string
pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}Z$
title: arrivalAt
description: UTC arrival timestamp in exact `YYYY-MM-DDTHH:mm:ssZ` form. It must be later than departure and consistent with the linked port-call chronology.
editor: textfield
fuelRecords:
type: array
minItems: 1
maxItems: 4
items:
type: object
additionalProperties: false
required:
- recordId
- consumptionStartAt
- consumptionEndAt
- fuelType
- massTonnes
- dataTruth
properties:
recordId:
type: string
pattern: ^[A-Za-z0-9][A-Za-z0-9._:-]{0,63}$
title: recordId
description: Unique identifier for this leg fuel-consumption record. Use 1–64 letters, digits, dots, underscores, colons, or hyphens, beginning with a letter or digit.
editor: textfield
consumptionStartAt:
type: string
pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}Z$
title: consumptionStartAt
description: UTC start of the fuel-consumption interval in exact `YYYY-MM-DDTHH:mm:ssZ` form. The interval must fall within the associated voyage leg.
editor: textfield
consumptionEndAt:
type: string
pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}Z$
title: consumptionEndAt
description: UTC end of the fuel-consumption interval in exact `YYYY-MM-DDTHH:mm:ssZ` form. It must follow the start and stay within the associated voyage leg.
editor: textfield
fuelType:
type: string
enum:
- HFO
- LFO
- MDO_MGO
- LNG
- BIO_LNG
- LPG_BUTANE
- LPG_PROPANE
- METHANOL
- BIOFUEL
- OTHER
title: fuelType
description: Fuel category for the supplied mass value. Choose the exact enum matching the evidence; unsupported calculation paths fail closed instead of guessing factors.
editor: select
massTonnes:
type: string
pattern: ^(0|[1-9][0-9]*)(?:\.[0-9]{0,5}[1-9])?$
title: massTonnes
description: Fuel mass in metric tonnes as a non-negative decimal string, for example `12.5`, with at most six significant fractional positions under the closed contract.
editor: textfield
dataTruth:
type: string
enum:
- measured
- buyer_reported
- estimated
title: dataTruth
description: 'Evidence quality for this fuel record: measured, buyer-reported, or estimated. The value is preserved so confidence and review gaps remain explicit.'
editor: select
title: fuelRecords
description: Array of 1–4 fuel-consumption evidence records for this leg. Intervals, fuel types, masses, and evidence quality feed the emissions calculation.
editor: json
title: legs
description: Ordered array of 1–8 voyage legs linking the supplied port calls. Each leg includes its UTC interval and bounded fuel-consumption evidence.
editor: json
berthRecords:
type: array
maxItems: 18
items:
type: object
additionalProperties: false
required:
- recordId
- portCallId
- consumptionStartAt
- consumptionEndAt
- fuelType
- massTonnes
- dataTruth
properties:
recordId:
type: string
pattern: ^[A-Za-z0-9][A-Za-z0-9._:-]{0,63}$
title: recordId
description: Unique identifier for this berth-consumption record. Use 1–64 letters, digits, dots, underscores, colons, or hyphens, beginning with a letter or digit.
editor: textfield
portCallId:
type: string
pattern: ^[A-Za-z0-9][A-Za-z0-9._:-]{0,63}$
title: portCallId
description: Exact `portCallId` where the berth consumption occurred. The referenced port call must exist and contain the supplied consumption interval.
editor: textfield
consumptionStartAt:
type: string
pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}Z$
title: consumptionStartAt
description: UTC start of berth fuel consumption in exact `YYYY-MM-DDTHH:mm:ssZ` form. It must fall within the linked port-call interval.
editor: textfield
consumptionEndAt:
type: string
pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}Z$
title: consumptionEndAt
description: UTC end of berth fuel consumption in exact `YYYY-MM-DDTHH:mm:ssZ` form. It must follow the start and remain within the linked port call.
editor: textfield
fuelType:
type: string
enum:
- HFO
- LFO
- MDO_MGO
- LNG
- BIO_LNG
- LPG_BUTANE
- LPG_PROPANE
- METHANOL
- BIOFUEL
- OTHER
title: fuelType
description: Fuel category for the berth-consumption mass. Choose the exact enum supported by the pinned calculation rules; unsupported paths fail closed.
editor: select
massTonnes:
type: string
pattern: ^(0|[1-9][0-9]*)(?:\.[0-9]{0,5}[1-9])?$
title: massTonnes
description: Berth fuel mass in metric tonnes as a non-negative decimal string, for example `1.25`, using the precision permitted by the closed contract.
editor: textfield
dataTruth:
type: string
enum:
- measured
- buyer_reported
- estimated
title: dataTruth
description: 'Evidence quality for this berth record: measured, buyer-reported, or estimated. It is retained in the output confidence and review-gap evidence.'
editor: select
title: berthRecords
description: Optional array of up to 18 berth fuel-consumption records linked to port calls. Supply an empty array when no berth consumption evidence is available.
editor: json
schemaVersion: 1
responses:
'200':
description: Actor run succeeded and payment settled
content:
application/json:
schema:
type: object
properties:
results:
type: array
items:
type: object
description: Actor output items — shape is actor-specific (varies per tool); see this operation's own requestBody schema/description for what the underlying actor produces.
meta:
type: object
properties:
run_ms:
type: integer
description: Actor run duration in milliseconds
item_count:
type: integer
description: len(results)
settled:
type: boolean
description: Whether the x402 payment was confirmed settled by the facilitator
transaction:
type:
- string
- 'null'
description: On-chain settlement transaction hash, null if unsettled
required:
- run_ms
- item_count
- settled
- transaction
required:
- results
- meta
'400':
description: Malformed PAYMENT-SIGNATURE header or request body
'402':
description: Payment required or invalid — see PAYMENT-REQUIRED header
'409':
description: Payment payload already used
'502':
description: Actor run failed
'504':
description: Actor run timed out
tags:
- Voyage Carbon Compliance Evidence