Skip to content

Developer path

Build around a useful onchain moment.

Define who needs the information, what coverage they expect, and how you will verify the result. Use the documentation to establish the integration boundary.

Read integration documentation View delivery proof model

Agent-native

Point your AI agent at Ekko's MCP server.

Any MCP client can search, create, update, and archive alerts and manage subscriptions. Access is authorized with OAuth and limited to the same permissions as your team. Contact support for your MCP endpoint and OAuth client.

ekko_alert_search
ekko_alert_context
ekko_alert_create
ekko_alert_update
ekko_alert_archive
ekko_subscription_subscribe
ekko_subscription_unsubscribe
Transport
Streamable HTTP
Authorization
OAuth
Tools
Seven alert actions

What engineers need to evaluate

Establish the user benefit and the boundaries of the supported release.

  1. 01

    Identify the relationship

    Distinguish provider subscribers, separately supplied UserWallets, and direct Individuals.

  2. 02

    Define the coverage

    WalletAlert follows the declared protocol. UserWallets follow their Alert Group scope.

  3. 03

    Confirm delivery

    Request the supported channel contract and observable failure states. UserWallets use webhooks only.

  4. 04

    Keep people in control

    Ekko reads, proposes, and prepares. People decide and execute transactions in their chosen application.

Plan the first useful result

Evaluate availability before turning a product concept into an implementation.

  • Integration scope

    Read the documentation for audience and coverage boundaries.

  • Delivery proof

    Separate an observed result from a hypothesized effect.

  • Release support

    Confirm installation and authentication with support for your release.

Start with one useful outcome.

Describe the user benefit and confirm the supported integration path before committing to a rollout.

Read integration documentation