Install Jentic One Beta

Connect the EtherDelta / ForkDelta API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the EtherDelta / ForkDelta API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fetherdelta%2Fetherdelta" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fetherdelta%2Fetherdelta" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with EtherDelta / ForkDelta API.

Pull a historical snapshot of ticker data for ERC-20 token pairs traded on ForkDelta

Reference the OpenAPI shape when migrating off legacy EtherDelta integrations

Document the rate-limit ceiling (6 concurrent connections, 12 reconnects per minute per IP) for any code still talking to the host

Identify the WebSocket fallback (wss://api.forkdelta.com) for clients that need live data rather than the REST snapshot

Use Cases

GET STARTED

Start building with EtherDelta / ForkDelta API

Explore with Jentic One

View OpenAPI Document

★ Historical archival snapshot of EtherDelta ticker data

Researchers studying early DEX market structure call /returnTicker once to capture whatever ticker data the legacy host still serves and persist it for later analysis. The endpoint returns price, last trade, and volume fields per token pair, enough to reconstruct a coarse view of the exchange's activity. Because the project is archived, treat any successful response as a snapshot, not a live feed.

GET /returnTicker once and persist the JSON response as a single timestamped snapshot file.

Migration audit from a legacy EtherDelta-based system

Teams retiring a wallet, analytics tool, or research notebook that still references the ForkDelta REST host audit their code against the documented shape so they can confidently swap in a current DEX data source. The spec shows there is only one REST endpoint, which simplifies the migration: every other call on the legacy host was over the socket.io WebSocket and must be replaced separately.

Compare the existing client's REST call list against this spec and flag any non-/returnTicker REST call as legacy-only and unsupported.

Liveness check on the archived ForkDelta host

Before relying on any old ForkDelta-derived data, an integrator pings /returnTicker to confirm whether the host still answers and whether the response shape has drifted. Because the project is archived, the result may be a non-2xx code or stale data, both of which are valuable signals for the integrator to abandon the dependency.

GET /returnTicker once with a short timeout and report whether the response is 2xx and contains ticker entries; otherwise mark the dependency as dead.

AI agent reasoning about a defunct DEX

An AI research agent asked about EtherDelta's API surface uses Jentic to resolve the operation, reads the spec to learn that only /returnTicker is REST and that everything else was socket.io, and surfaces that to the user with the WebSocket URL and rate limit. The agent does not need to scrape archived blog posts to answer.

Search Jentic for 'EtherDelta ticker', read the operation description, and reply with the REST path /returnTicker, the WebSocket fallback wss://api.forkdelta.com, and the documented rate-limit ceiling.

Key Endpoints

1 endpoints — jentic publishes the only available openapi specification for etherdelta / forkdelta api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/returnTicker

Return ticker data for all traded ERC-20 token pairs

GET

/returnTicker

Return ticker data for all traded ERC-20 token pairs

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the EtherDelta / ForkDelta API by hand means finding the surviving forkdelta.com host, discovering the legacy /returnTicker shape from archived posts, and handling retries yourself. Through Jentic you install once, import the EtherDelta / ForkDelta API from the API Directory, and your agent calls it with no credential to manage.

Permission scoping

The EtherDelta / ForkDelta API exposes a single read-only ticker snapshot, so scope the agent to that one GET /returnTicker operation. You choose which operations are allowed, so nothing beyond reading the ticker snapshot runs unless you add it.

Credential isolation

The /returnTicker endpoint needs no credential, so there is nothing to store; if the operation ever required auth, that credential would be stored once, encrypted, by your own Jentic One instance and injected at execution time.

Intent-based discovery

Agents search Jentic by intent such as 'get the ForkDelta ticker snapshot', and Jentic returns the GET /returnTicker operation with its input schema so the agent calls the right endpoint without hunting through archived blog posts.

FAQs

Specific to using EtherDelta / ForkDelta API through Jentic.

Why is there no official OpenAPI spec for EtherDelta / ForkDelta API?

EtherDelta and ForkDelta did not publish an OpenAPI specification, and the projects are now archived. Jentic generates and maintains this spec so that AI agents and developers can reason about the legacy surface via structured tooling. It is validated against the documented API and kept available for migration and archival use. Get started with Jentic One, the self-hosted execution layer.

What authentication does the EtherDelta / ForkDelta API use?

The /returnTicker REST endpoint is unauthenticated; no API key or token is required. Through Jentic the operation is exposed as a public-data tool, with rate-limit guidance applied at the gateway.

Is the EtherDelta API still active?

EtherDelta itself ceased operations and ForkDelta, its successor, was archived as of December 2022. Treat any successful response from /returnTicker as a stale snapshot rather than live exchange data, and prefer a current DEX source for fresh prices.

What are the rate limits for the EtherDelta / ForkDelta API?

The documented limit is 6 concurrent connections and 12 reconnects per minute per IP address. Because the project is archived, exceeding these limits is more likely to result in silent failures than enforcement, but you should still respect them for politeness toward whatever host is still answering.

How do I retrieve the ForkDelta ticker through Jentic?

Search Jentic for 'ForkDelta ticker snapshot'. Jentic returns GET /returnTicker. Execute it with no parameters; the response is a JSON object keyed by token pair, where each value contains last price, bid, ask, and 24-hour volume.

Can I place trades through this API?

No. The REST surface only exposes /returnTicker. All trading actions on the legacy exchange happened over the socket.io WebSocket at wss://api.forkdelta.com, which is outside this OpenAPI document and is not supported by the archived project.

Can I limit what my agent is allowed to do with the EtherDelta / ForkDelta API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials your agent may use. This API exposes a single read-only GET /returnTicker operation, so you can scope the agent to just that ticker-snapshot call and nothing else runs unless you add it. Since the endpoint needs no credential, there is nothing to store, and the agent can only read the ticker data you have allowed.

EtherDelta / ForkDelta API

Name: EtherDelta / ForkDelta API
Brand: EtherDelta / ForkDelta API
Availability: InStock

Agent-ready OpenAPI document · curated by JenticFinanceBankingnone1 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Retrieve the legacy ForkDelta ticker snapshot for ERC-20 token pairs from the now-archived EtherDelta successor exchange.

Use for: Retrieve the last available ticker snapshot from the ForkDelta REST endpoint, Find historical price data for an ERC-20 token traded on EtherDelta, Check whether the EtherDelta API is still responding, Get the REST surface shape when migrating off a legacy EtherDelta integration

Not supported: Does not handle order placement, account balances, or live streaming - use for reading the legacy /returnTicker snapshot only.

Jentic publishes the only available OpenAPI specification for EtherDelta / ForkDelta API, keeping it validated and agent-ready. EtherDelta was an early Ethereum-based decentralized exchange for ERC-20 tokens, succeeded by ForkDelta. The exchange and its successor are both archived: most live trading happened over a socket.io WebSocket at wss://api.forkdelta.com, with only a single REST ticker endpoint at /returnTicker. This spec documents that lone REST endpoint so historical analysts and archivists can still pull a snapshot of the ticker. Status: defunct - ForkDelta was archived in December 2022.

Jentic One on Github View OpenAPI Document