API Overview

The Icebreaker public API gives builders access to profile, credential, and social graph data on the platform.

Base URL

https://app.icebreaker.xyz/api/v1/

All endpoints accept GET requests and return JSON. See the API Reference for the full endpoint list.

Authentication

Profile data that users have chosen to make public is accessible without an API key or signup. You can query public profiles, credentials, and social connections without any authentication.

Some operations require authentication:

Credentialing endpoints (attesting and storing credentials via PUT /credentials) require a Bearer token
Higher rate limit access requires an API key

To obtain a Bearer token or API key, contact [email protected].

Supported lookup types

You can look up an Icebreaker profile by any of the following identifiers:

Identifier	Endpoint
ENS name	`GET /ens/{ensname}`
ETH wallet address	`GET /eth/{walletaddress}`
Farcaster ID (FID)	`GET /fid/{fid}`
Farcaster name	`GET /fname/{fname}`
Social channel and username	`GET /socials/{channeltype}/USERNAME`

Supported channel types for /socials include linkedin, twitter, github, farcaster, and ens. See the API Reference for the full list.

Rate limits

Public endpoints are rate-limited to prevent abuse. If you are building a production integration that requires higher limits, contact [email protected].

Quick example

curl --request GET \
     --url https://app.icebreaker.xyz/api/v1/ens/j4ck.eth \
     --header 'accept: application/json'

Returns the Icebreaker profile, verified credentials, and connected social accounts for the ENS name j4ck.eth.

REST API vs. MCP

If you are building an application or pipeline that calls Icebreaker programmatically, the REST API is the right tool. If you are working inside an AI assistant like Claude or ChatGPT and want to query your network in natural language, the MCP server is a better fit.