etherfuse.com valid

Etherfuse API

For agents: Etherfuse API docs for buying, selling and swapping stablecoins and yield-bearing stablebonds with fiat, with sandbox and webhooks.

stablecoin apistablebondson-ramp off-rampfiat to stablecoinwebhooks

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-27T10:18:51.901Z. Cached copy · Source on etherfuse.com

# Etherfuse API

- [Introduction](https://docs.etherfuse.com/v2/index.md): On/off-ramps and swaps: buy and sell stablecoins and yield-bearing stablebonds with fiat, or swap one asset for another.
- [Quickstart](https://docs.etherfuse.com/v2/quickstart.md): From a sandbox API key to your first order: register payment accounts, quote, order, and get webhooks.
- [Initial Setup](https://docs.etherfuse.com/v2/initial-setup.md): Create a sandbox business account, get an API key, and make your first call
- [Sandbox Reference](https://docs.etherfuse.com/v2/test-environment.md): Everything that behaves differently in the Etherfuse sandbox: base URLs, test data, simulated deposits, and testnet tokens.
- [V1 → V2](https://docs.etherfuse.com/v2/migration-guide.md): Why to switch to v2, and how to migrate from v1: endpoint replacements, request fields, order statuses and webhooks.
- [How it works](https://docs.etherfuse.com/v2/overview.md): How an Etherfuse integration fits together: conventions, payment accounts, quotes, orders and webhooks.
- [Webhooks](https://docs.etherfuse.com/v2/webhooks.md): Subscribe to order, payment account, KYC and KYB events. Verify signatures and handle retries.
- [JWT User Authentication](https://docs.etherfuse.com/v2/guides/jwt-authentication.md): Authenticate your users to Etherfuse with short-lived JWTs you sign, and launch them straight into the app.
- [User Launch Flows](https://docs.etherfuse.com/v2/guides/user-launch-flows.md): Every in-app flow you can launch a user into: the scope and target each one uses, and what to know about each.
- [Authentication errors](https://docs.etherfuse.com/v2/guides/authentication-errors.md): What each JWT auth and launch error means, and how to fix it.
- [Embedded Wallets](https://docs.etherfuse.com/v2/guides/embedded-wallets.md): Move on-chain assets for your users through non-custodial embedded wallets, without anyone touching gas, trustlines, or transaction construction.
- [Embedded Wallets](https://docs.etherfuse.com/v2/guides/embedded-wallets.md): Move on-chain assets for your users through non-custodial embedded wallets, without anyone touching gas, trustlines, or transaction construction.
- [Embedded Wallets Sandbox Onramp](https://docs.etherfuse.com/v2/guides/embedded-wallets-walkthrough.md): A minimal server-side script that runs an embedded-wallet onramp in sandbox, from wallet registration to the signed claim authorization.
- [Verifying Webhooks](https://docs.etherfuse.com/v2/guides/verifying-webhooks.md): How to verify webhook signatures to ensure payloads are authentic
- [Swaps](https://docs.etherfuse.com/v2/guides/testing-swaps.md): How to test token-to-token swap flows in the sandbox environment
- [Onramps](https://docs.etherfuse.com/v2/guides/testing-onramps.md): How to test onramp flows in the sandbox environment
- [Offramps](https://docs.etherfuse.com/v2/guides/testing-offramps.md): How to test offramp flows in the sandbox environment
- [KYC Overview](https://docs.etherf
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=etherfuse.com · GET /v1/domain/etherfuse.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for etherfuse.com:
1. POST https://agentwebmap.com/v1/sites/etherfuse.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://etherfuse.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/etherfuse.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/etherfuse.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.