SEDNA
SEDNA is the operating system for shipping — a communications and workflow platform that unifies email, voyage and trade operations, and document handling for maritime, commodity trading and logistics teams. Its API (version 2019-01-01) exposes messages, contacts, teams, users, job references, category tags, events and workflows over a JSON:API-style REST interface secured with OAuth 2.0 client-credentials, letting developers automate inbox routing, tagging, subscriptions and third-party integrations. Backed by Insight Partners.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles SEDNA the way a machine reads it — 22 machine-readable artifacts across 17 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — SEDNA scores 40.7/100 (thin), with a separate agent-readiness read of 69/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
How we profile SEDNA
Each block below is one kind of artifact we hold for SEDNA. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 17
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
SEDNA Authentication API
The Authentication API from SEDNA — 1 operation(s) for authentication.
SEDNA Category Tag API API
The Category Tag API API from SEDNA — 7 operation(s) for category tag api.
SEDNA Comment API API
The Comment API API from SEDNA — 1 operation(s) for comment api.
SEDNA Company API API
The Company API API from SEDNA — 1 operation(s) for company api.
SEDNA Contact API API
The Contact API API from SEDNA — 8 operation(s) for contact api.
SEDNA Document API API
The Document API API from SEDNA — 1 operation(s) for document api.
SEDNA Download API API
The Download API API from SEDNA — 4 operation(s) for download api.
SEDNA Event API API
The Event API API from SEDNA — 9 operation(s) for event api.
SEDNA Job Reference API API
The Job Reference API API from SEDNA — 7 operation(s) for job reference api.
SEDNA Keyword API API
The Keyword API API from SEDNA — 3 operation(s) for keyword api.
SEDNA Message API API
The Message API API from SEDNA — 19 operation(s) for message api.
SEDNA Saved Search API API
The Saved Search API API from SEDNA — 2 operation(s) for saved search api.
SEDNA Team API API
The Team API API from SEDNA — 9 operation(s) for team api.
SEDNA Template API API
The Template API API from SEDNA — 2 operation(s) for template api.
SEDNA User API API
The User API API from SEDNA — 16 operation(s) for user api.
SEDNA Vessel API API
The Vessel API API from SEDNA — 1 operation(s) for vessel api.
SEDNA Workflow API API
The Workflow API API from SEDNA — 2 operation(s) for workflow api.
Scroll within the panel for all 17 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
sedna-mcp.yml
MCP SERVERSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for SEDNA — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Access & Security 4
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/sedna · machine-readable index on apis.io