Developer API
Upload media, publish metadata, prepare a launch transaction, then index the token—all with ordinary HTTP and standard Arc signing.
Quick start
- Upload an image in any aspect ratio.
- Create the metadata document.
- Prepare an unsigned launch transaction.
- Sign and broadcast on chain ID 5042.
- Read the indexed token and live graduation progress.
1. Upload image
curl -X POST $BASE_URL/api/arc/v1/images \
-F "image=@token.png"2. Create metadata
curl -X POST $BASE_URL/api/arc/v1/metadata \
-H "content-type: application/json" \
-d '{"name":"Degen Cat","symbol":"DEGEN","image":"/api/image/IMAGE_ID"}'3. Prepare launch
curl -X POST $BASE_URL/api/arc/v1/launch/prepare \
-H "content-type: application/json" \
-d '{"name":"Degen Cat","symbol":"DEGEN","metadataUri":"METADATA_URI","feeRecipient":"0x...","initialBuyEth":"0.1"}'initialBuyEth is a legacy compatibility field name. On Arc, it means an optional initial buy denominated in USDC and accepts at most 6 decimal places.
The response contains chainId, to, data, and value. Sign it with your own wallet. The API never receives a private key.
4. Read launches
curl "$BASE_URL/api/arc/v1/tokens?limit=50"
curl "$BASE_URL/api/arc/v1/tokens/0xTOKEN"
curl "$BASE_URL/api/arc/v1/tokens/0xTOKEN/trades?limit=50"Progress is returned as basis points: 0 to 10000. It follows the V3 pool's USDC balance, and graduation becomes permanent as soon as the indexed all-time-high pool balance reaches the configured target. No keeper transaction is required.
Reliability
- Cursor pagination is stable by launch block.
- Robinhood, Arc, Stable, X Layer, and HyperEVM use separate indexers and databases.
- Read responses use short caching and stale-while-revalidate.
- All endpoints support browser CORS.
- Errors use stable codes and human-readable messages.
