Your intent, built with Chainlink.

Mainnet strategies and automated orders

Configure conditional execution for price-triggered or recurring swaps, token allocation, approved contract steps on Base, or LINK transfers to Robinhood. Review immutable permissions, deploy your wallet, fund it and activate monitoring.

Open automated orders for limit-price and time-sliced orders. Review exact amounts and permissions in the native order panel, then manage history and cancellations here. Time-sliced orders require a configured Safe wallet. This is separate from arbitrary Chainlink-triggered drafts.

Open mainnet execution for immediate wallet-signed swap and bridge routes. Review minimum output and fees, then approve each wallet action. Chainlink Intents fees are always zero. Gas and routing fees are separate. Saved conditional drafts are not activated by this flow.

From instruction to inspectable intent

Describe a financial intention or choose a template. The deterministic parser produces an editable specification. Review the condition, reference price, amount, route, action and limits. Simulate against available Chainlink observations, then save a local draft.

Local drafts remain in this browser. Export JSON for backup or import it from Build. Connecting a wallet reads balances; it does not sign an intent or grant spending permission.

What is available today

Chainlink data, CCIP routes and CRE architecture.

The intent specification is the common boundary between the composer, condition evaluator, workflow adapter and settlement contracts. Chainlink Data Feeds provide timestamped onchain observations. CRE is the intended orchestration runtime; a local simulation is never represented as DON execution.

CCIP configuration is centralized and sourced from the official directory. Router and chain selector verification does not verify a specific token pool or lane. The conditional LINK flow verifies its token route before deployment; custom destination calls need their own integration.

Robinhood Chain mainnet (4663) is the home environment. Testnet (46630) is used by deployment scripts. No production Chainlink Intents contract address is assumed.

Explicit authorization, bounded execution

Every specification contains a maximum amount, asset, source, destination, slippage bound, expiry, cooldown and maximum execution count. Execution wallets enforce token caps, fee caps, expiry and cooldown. Strategy wallets also enforce approved call data, temporary allowances and minimum outputs atomically. Immediate stock-token trades use the separate Stock Tokens flow, subject to eligibility, asset availability and executable quotes. They do not activate arbitrary stock-price drafts.

• Missing, future-dated, invalid or stale oracle observations cannot authorize execution.
• Percentage conditions need a reference price. Portfolio, volatility and schedule conditions remain indeterminate until their adapters are configured.
• Stock Token prices reflect total return value, including corporate-action multipliers. They are not the same as underlying share prices.
• Production execution requires sequencer checks, token oracle pause checks where applicable, verified adapters and contract review.
• Simulation never creates a receipt, message ID, or completed transaction.

API and persistence

Public reads: GET /api/health, GET /api/templates, GET /api/data/assets, GET /api/ccip/:messageId. Public simulation: POST /api/simulate with an IntentSpec body.

Private operator endpoints require Authorization: Bearer API_TOKEN (minimum 32 characters) and PostgreSQL. Run migrations/001_initial.sql before use. Missing authentication returns 401; missing storage returns 503. The service never silently accepts ephemeral server records.

Private routes: list/create /api/intents, get /api/intents/:id, history /api/intents/:id/history, and POST actions simulate, pause, resume, cancel. Resume returns to draft, not active automation. This is a single-operator API, not wallet-authenticated multi-tenant storage.

Requests are validated and capped at 32 KB. Public endpoints have a best-effort per-instance limit of 60 requests/minute; use a shared rate limiter or application firewall for distributed production limits.

TypeScript SDK

The package at packages/sdk exports LinkIntents, Intent and IntentSpec. It is a repository package and has not been published to npm.

Methods include createIntent, listIntents, getIntent, cancelIntent, pauseIntent, resumeIntent, simulateIntent, getExecution, getCCIPStatus, getIntentHistory and subscribeToIntent. Subscriptions poll with an explicit cleanup function. The operator token must remain server-side.

Signed webhook delivery

Configure one operator-controlled HTTPS endpoint and a minimum 32-character signing secret. Events are queued in PostgreSQL; POST /api/webhooks/dispatch requires operator authentication. Delivery retries five times with exponential backoff. The dispatcher must be scheduled by your infrastructure.

Verify X-Linkintents-Signature as HMAC-SHA256 over timestamp + "." + rawBody, using X-Linkintents-Timestamp. Reject timestamps older than five minutes and deduplicate X-Linkintents-Event-Id. Delivery is at least once. Only real events are emitted; execution events require deployed execution infrastructure.

Verified sources

Configuration verified on 2026-09-28. Network and contract support can change; reverify before enabling sends.

Chainlink Intents is an independent application built with Chainlink. It is not owned, operated, sponsored or endorsed by Chainlink Labs or Robinhood.