DCA orders — dollar cost average into any token

DCA orders for crypto. Split buys over time, gasless, oracle-protected, 8 EVM chains.

Spot Advanced Swap Orders

Dollar cost average into any token with gasless DCA orders — split buys over time across 8 EVM chains, powered by decentralized TWAP execution. Use this skill when the agent needs to turn user intent into a final Spot order payload on a supported EVM chain. It covers order-shape selection, param normalization, typed-data population, approval guidance, signing, submission, query, and cancellation. This bundle is instruction-only: build everything locally from the bundled markdown and JSON assets, then submit only the final signed payload. Execution remains decentralized, non-custodial, oracle-protected, immutable, audited, and battle-tested onchain.

Supported Chains

1. Ethereum - 1 - adapter 0xC1bB4d5071Fe7109ae2D67AE05826A3fe9116cfc
2. BNB Chain - 56 - adapter 0x67Feba015c968c76cCB2EEabf197b4578640BE2C
3. Polygon - 137 - adapter 0x75A3d70Fa6d054d31C896b9Cf8AB06b1c1B829B8
4. Sonic - 146 - adapter 0xD87ee28806bc0060789C4789F123647f4Df25A6C
5. Base - 8453 - adapter 0xc64d6E64A713EfbbCcB14413479c56461F9c0b77
6. Arbitrum One - 42161 - adapter 0x6F1002141Fcb5d3A3aA8b12A49e6e7DCE5661ae9
7. Avalanche - 43114 - adapter 0xc64d6E64A713EfbbCcB14413479c56461F9c0b77
8. Linea - 59144 - adapter 0x55E4da2cd634729064bEb294EC682Dc94f5c3f24

Relay

1. Submit signed orders with POST https://agents-sink.orbs.network/orders/new.
2. Query orders with GET https://agents-sink.orbs.network/orders; see references/lifecycle.md for filters, polling, and cancellation follow-up.

Workflow

1. Read references/quickstart.md for the minimum end-to-end flow.
2. Use references/params.md to map user intent into params, defaults, validation, and order-shape fields.
3. Use references/sign.md to fill the template, handle approval, sign, and submit.
4. Use references/lifecycle.md for relay query semantics, status polling, and cancellation.
5. Use references/examples.md only when the final relay payload shape is still unclear.
6. Use assets/token-addressbook.md only for optional token alias lookup on supported chains.
7. Use assets/repermit.template.json as the canonical typed-data shape.
8. Treat ## Supported Chains as the authoritative source for chain support and per-chain adapters.
9. Treat ## Relay as the authoritative relay endpoint list.

Guardrails

1. ## Supported Chains is authoritative for chain support and per-chain adapters.
2. ## Relay is authoritative for relay endpoints.
3. assets/token-addressbook.md is a convenience alias list only. It does not expand chain support or override explicit user-provided addresses.
4. This skill is instruction-only. Do not fetch or execute external helper code.
5. Normalize params with references/params.md before touching the template.
6. Replace only the <...> placeholders in assets/repermit.template.json. Keep the fixed protocol fields already in the template unchanged.
7. Default approval guidance is exact approve(..., input.maxAmount). Standing maxUint256 approval is opt-in convenience for repeat use, not the default suggestion.
8. Submit only the final signed payload as described in references/sign.md.

Agent Contract

1. Turn the user request into a params JSON object using references/params.md.
2. Normalize params locally, including defaults, rounding, and order-shape fields.
3. Confirm chainId is listed in ## Supported Chains, then populate assets/repermit.template.json from the normalized params and replace <ADAPTER> with that chain's listed adapter.
4. Handle approval, signing, and submission exactly as described in references/sign.md, and forward the returned signature unchanged.
5. Query and cancel exactly as described in references/lifecycle.md.