chain — Access — endpoint —

Developer console

Get started

From zero to a response four steps

  1. Point at the instance

    shell 
    # the index: every route, its price, and how to pay
curl -s http://127.0.0.1:8787/v1

  2. Take a key, or pay per call

    shell — on the server host 
    # issue a key on the Free plan
node src/key-cli.js create --plan free --label "my integration"

# it prints the raw key once — the server only stores its SHA-256
# revoke it later with the prefix it shows you
node src/key-cli.js revoke --prefix arc_1a2b3c4d5e6f
    Shown once, never again.

  3. Call a route

    shell 
    curl -s -H "X-API-Key: $ARC_KEY" \
  http://127.0.0.1:8787/v1/network

# or, equivalently
curl -s -H "Authorization: Bearer $ARC_KEY" \
  http://127.0.0.1:8787/v1/network
    200 OK
    {
  "chain": { "name": "Arc", "chainId": 5042 },
  "head": 21264878,
  "tokens": 3200,
  "alerts": 15
}

  4. Watch your quota

Plans

What each plan includes —

Credits, not calls.
Keys
Keys on record
—
Active
—
Revoked
—
Expired
—
Requests served
—
Credits charged
—

Managing keys issued and revoked from the host, by design

shell — on the server host
issue a key
node src/key-cli.js create --plan pro --label "acme desk"

list keys
node src/key-cli.js list

revoke a key
node src/key-cli.js revoke --prefix arc_1a2b3c4d5e6f

the plan table, straight from the source of truth
node src/key-cli.js plans
Revocation is fast on purpose.