Public API

Arcantis has a public API so you can launch a token from a script, a trading bot, an AI agent, or your own front-end. A token launched this way is identical to one launched on the website: same factory contract, same 70/20/10 fee split, same permanently locked liquidity.

No API key. No sign-up. Nothing here moves money or exposes anything private, so there is nothing to gate.

Using it from an AI agent

There's a ready-made skill file — drop it into Claude Code, OpenCode, Hermes, OpenClaw or anything else that loads markdown skills, and the agent knows the whole flow without you explaining it:

https://arcantis.fun/skills/arcantis/SKILL.md

For Claude Code, save it as .claude/skills/arcantis/SKILL.md in your project (or ~/.claude/skills/ to have it everywhere). Most other frameworks take the raw URL directly.

There's also an llms.txt at the root, which is what agents look for when they want to find their way around a site on their own.

The flow

1. POST /api/v1/launch/prepare with your token's details
2. Sign and send the approval transaction it returns, if there is one
3. Sign and send the launch transaction
4. Read the token address from the TokenLaunched event in the receipt
5. Optionally POST an image and description to the metadata endpoint

Get the current rules

curl https://arcantis.fun/api/v1/config

Returns the chain, contract addresses, and the live launch rules — the fee, the supply bounds, the starting market cap. Read these rather than hardcoding them; they're read from the contract on every request and can change.

Prepare a launch

curl -X POST https://arcantis.fun/api/v1/launch/prepare \
  -H 'Content-Type: application/json' \
  -d '{
    "name": "My Coin",
    "symbol": "MYC",
    "totalSupply": "1000000000",
    "creatorAddress": "0xYourWallet",
    "devBuyUsdc": "25",
    "venue": "uniswap-v3"
  }'

Amounts are decimal strings, not raw integers — write "25" for $25, not "25000000". Values coming back are raw integers as strings, because a JSON number would silently round a supply of 1e21.

You get back:

{
  "chainId": 5042002,
  "transactions": {
    "approval": { "to": "0x36…", "data": "0x095ea7b3…", "value": "0" },
    "launch":   { "to": "0x60…", "data": "0x1f6a5b96…", "value": "0" }
  },
  "cost": {
    "launchFeeUsdc": "1000000",
    "totalUsdcRequired": "26000000",
    "sufficientBalance": true
  }
}

approval is null when your allowance is already enough. When it isn't null, send it first and wait for it to confirm — the factory pulls USDC from your wallet, and the launch reverts with transfer amount exceeds allowance if you skip it.

sufficientBalance is reported, not enforced. If it's false the transaction is still built, on the assumption you're about to fund the wallet.

Send it

import { createWalletClient, http, parseEventLogs } from "viem";
import { privateKeyToAccount } from "viem/accounts";

const account = privateKeyToAccount(process.env.PRIVATE_KEY);
const wallet = createWalletClient({ account, transport: http(RPC_URL) });

const { transactions } = await fetch(".../api/v1/launch/prepare", { ... }).then(r => r.json());

if (transactions.approval) {
  const hash = await wallet.sendTransaction(transactions.approval);
  await publicClient.waitForTransactionReceipt({ hash });
}

const hash = await wallet.sendTransaction(transactions.launch);
const receipt = await publicClient.waitForTransactionReceipt({ hash });
// TokenLaunched in the receipt logs carries your new token's address

Add an image and description

These aren't on-chain, so they're a separate call after the launch confirms:

curl -X POST https://arcantis.fun/api/tokens/0xYourToken/metadata \
  -H 'Content-Type: application/json' \
  -d '{ "name":"My Coin", "ticker":"MYC", "totalSupply":"1000000000000000000000000000",
        "creatorAddress":"0xYourWallet", "imageUrl":"https://…", "description":"…",
        "ammVenue":"uniswap-v3", "launchType":"quick" }'

Do this straight after launching. It makes your token appear on the site immediately rather than waiting for the indexer, and sets the venue so the first buys route correctly.

Reading data

These are open too, and need nothing:

Errors

Validation failures return 400 with the offending field named:

{ "error": "invalid_request", "field": "totalSupply",
  "message": "totalSupply must be between … raw units (18 decimals)." }

Parameters are checked against the live contract rules, so a request that returns 200 should not revert for a reason we could have caught. Gas, balance and network conditions are still yours to handle.