Dialect
Dialect is a Web3 UX infrastructure company on Solana that provides onchain transactions and notifications native to any digital experience. Its two flagship products are Blinks (Blockchain Links — one-click, embeddable onchain transactions powered by a Standard Blinks Library of 40+ protocol integrations including Jupiter, Kamino, Drift and DeFiTuna) and the Alerts Stack (real-time, multi-channel notifications across push, email, Telegram and an in-app universal inbox, with event detection for price-change and trending-token signals). Dialect also exposes a Markets & Positions API for real-time DeFi rates, TVL and wallet position tracking, plus a hosted MCP server for agents. The developer surface spans three REST APIs (Alerts V2, Blinks, Markets), TypeScript/React SDKs, a no-code dashboard, and an open-source monitor framework. Backed by Electric Capital and Multicoin Capital.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Dialect the way a machine reads it — 14 machine-readable artifacts across 9 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 — Dialect scores 52.8/100 (developing), with a separate agent-readiness read of 71/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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Dialect
Each block below is one kind of artifact we hold for Dialect. 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 9
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.
Dialect Blink API
The Blink API from Dialect — 2 operation(s) for blink.
Dialect Blink Data Table API
The Blink Data Table API from Dialect — 1 operation(s) for blink data table.
Dialect Blink Lists API
The Blink Lists API from Dialect — 1 operation(s) for blink lists.
Dialect Blink Preview API
The Blink Preview API from Dialect — 1 operation(s) for blink preview.
Dialect Channels API
The Channels API from Dialect — 7 operation(s) for channels.
Dialect Inbox API
The Inbox API from Dialect — 17 operation(s) for inbox.
Dialect Markets API
The Markets API from Dialect — 3 operation(s) for markets.
Dialect Positions API
The Positions API from Dialect — 3 operation(s) for positions.
Dialect Send API
The Send API from Dialect — 4 operation(s) for send.
Scroll within the panel for all 9 ·
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.
dialect-mcp.yml
MCP SERVEREvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Dialect Webhooks
ASYNCAPISecurity 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.
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 Dialect — 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 5
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
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
Other 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/dialect · machine-readable index on apis.io