Garp
Launch a token
Web app and Token API
GET STARTED

Build with Garp

For holders, communities and creators. Explore the web app, understand a token, contribute to its growth, and find your next step.

YOUR PROJECT. CONNECTED.

Context in.
Clarity out.

Research the market. Find your people.
Create something worth sharing.

Discover→Create→Launch→Grow

What is Garp?

Garp helps token projects research their audience, create content and prepare outreach. Add your existing token or launch one, then use Garp’s web tools or connect your AI client through MCP. Paid API credits power the AI work; public token tracking is free.

Choose your starting point

GET STARTED

Connect Garp MCP

Use Garp’s project context, research, content and outreach tools from your AI client.

Connect your AI client

  1. Open your Garp workspace. Sign in using the wallet menu. A connected wallet signs one free message to verify access; an existing verified session is reused.
  2. Choose Explore a token idea to start before launch, or Add existing token to use a contract address or Solana mint. An idea project needs no token, X account or chosen name.
  3. If your project has no API credits, choose Buy credits. PAYG and the Starter, Growth and Scale plans match homepage pricing. Review the selected project and payment in checkout.
  4. Choose Connect MCP, then Create connection key. Create a private connection key and copy your project MCP URL.
  5. Add the URL and bearer key to Codex, Hermes or another compatible MCP client. Follow the client setup guide for configuration details.

Save the private key when it is created; the full key is shown once. Keep it out of public posts and repositories.

Give your agent a first task

Load my Garp project and summarize what you know. Research the audience and draft a post using verified project facts. Show me the draft before publishing.

Your agent can use available Garp tools and project memory. Results depend on the project’s connected sources and available data. Owner actions still require the eligible wallet’s authorization.

One project balance

The same project credits power Garp’s web tools, MCP requests and hosted work. Select the project on your dashboard to see its balance and buy credits for it, including before a token exists. Each project can link one token; adding another token creates a separate project balance.

Attaching a token to an existing unbound project keeps that project’s credits and MCP keys. Public token tracking is free. Launch and network fees, and your AI client’s model usage, are separate.

GET STARTED

Explore the web app

A practical map of Garp’s research and project tools.

Leaderboard and token pages

Open the leaderboard to explore indexed tokens and creator earnings. Search with a contract address or Solana mint to identify the exact asset. Names and tickers can be shared by unrelated tokens.

A token page combines its profile and links with available market data, trading activity, holders and creator fees. Read the displayed time window beside each metric. A 24 hour volume figure and an all time fee total describe different periods. Estimated fees and missing data should stay labeled when you use them in a report.

KOLs and audience discovery

KOLs is Garp’s public directory of people and project accounts. Explore posts, relationships and activity to understand why an account could be relevant. A high rank or a large follower count does not establish fit. Read the underlying evidence before making a shortlist.

Garp agents

Read the complete web app agent guides for step by step instructions, controls, outputs and requirements.

Garp’s content agent creates project content and image specifications. Use the content agent to review, edit and export artwork. Other site agents cover AI visibility, outreach suggestions, mentions and whale activity. Their availability depends on the token’s data and connected sources.

My tokens and project information

Use your Garp workspace to see your tokens, add an existing token, launch another token, view API credits and buy a plan or credit pack. Choose a project to open its web tools or connect MCP. Publishing official information requires an eligible owner wallet signature. Plans match homepage pricing.

GET STARTED

For holders and communities

Research a token, follow its progress and contribute to the community with Garp.

Start with the token, not an owner account

Garp is for holders, community members and creators. Open the leaderboard and search for a contract address or Solana mint. You do not need to be the creator to explore a token’s public page. Check the exact address before using its data or sharing its content.

Use the available price chart, trades, creator fee history, project links and social context to understand what is happening. Compare time windows and check source timestamps. Holding a token does not make every protected report or owner control available.

Use the agents to contribute

Where token access and data availability allow, holders can use the web agents to understand and support a project. Garp’s content agent can help prepare a post and image, Mentions can surface conversations, GEO can suggest useful project information, and Reach or Whale watch can provide context for research.

Review drafts before sharing from your own account. Adapt founder or team wording to your actual role: say you are a holder or community member when that is the case. Verify product claims and do not present your draft as an official team announcement.

Community access and owner permissions

ActivityWhat determines access
Explore public token dataAvailable indexed data and public sources; being the creator is not required.
Use AI agent featuresYour plan and available Garp service credits, plus each feature’s data requirements. Owner actions still require verification.
Buy AI creditsChoose a plan or pay as you go on Pricing. Credits belong to the selected project.
Change official information or connect private sourcesThe eligible owner’s authorization, not simply holding the token or paying for access.
Claim fees or manage a lockThe relevant wallet role and contract permissions.

Buying service credits does not transfer token ownership, fee rights or permission to edit official profiles.

Read the evidence carefully

Creator earnings describe payouts to the creator or configured recipient. They are not automatically a holder dividend. A price move, large wallet trade or social mention does not by itself explain why someone acted.

Use the available lock details, ownership information and source evidence as context. Missing reports remain unknown, and a suggested contact is not proof that someone supports the project. Share the source and time window alongside any figures you discuss.

WEB APP AGENTS

Web app agents

Tools for holders, communities and creators inside a token’s Garp workspace.

Open your token workspace

Find the token on the leaderboard or search its contract or mint. Holders and community members can explore public information and available agent features without being the creator. For owner actions, open that token’s workspace and connect the eligible wallet. Verify the exact contract before using or sharing its content.

The workspace brings together Content agent, Coin, Analytics, Things to do, Reach and token aware chat. On a phone, switch between panels. In Things to do, expand an agent row to see its evidence, editable drafts and available actions.

Choose an agent

Community access and owner actions

The agents serve holders and community contributors as well as the team. Read For holders and communities for a starting workflow and an explanation of permissions. When using drafts from your own account, adjust team or founder language to accurately describe your role.

If an AI tool asks for credits, open Pricing to see the current plans. Buying credits does not grant ownership or signing permission.

Owner verification is separate. Enrichment, private reports, profile updates and other protected actions may ask for a wallet signature. Transactions such as claiming or locking use their own wallet review. Buttons depend on the chain, launchpad, connection state and wallet role.

Read the state before acting

A badge counts available drafts or tasks. It is not a count of completed sends. “Written by the agent” identifies generated output; “template” or “starter drafts” identifies a fallback. Empty results can mean there are no eligible targets, required data is missing, or a provider is unavailable.

Copy, Reply, DM on X and Open X help you take the next step. They do not establish that a message was sent. Review the final text, make your relationship to the project clear, and verify the result on the destination platform.

WEB APP AGENTS

Content agent

Create, edit and export posts with artwork grounded in your project.

Open the content agent

  1. Select your token and open Content agent, or expand Content agent in Things to do and choose Open content agent.
  2. Review the Sources row and source status cards. Add missing Website, X account and GitHub links through Project info. The owner can connect Database data through Supabase.
  3. Wait for the dated set of posts. Each card includes an angle, editable X post, image preview and source note.

What the content agent reads

Garp’s content agent draws on the token’s published information, website, available X posts, GitHub activity, market and holder observations, and connected app or website analytics when available. Selected database tables can provide product activity and growth context. Recent content history helps inform subsequent drafts.

Read the source note on each post. A business metric includes its source and period. A source card that is missing or unavailable is not evidence of zero activity. Starter drafts can appear when generation is unavailable; review them with the same care as generated copy.

Edit copy and artwork

Edit the X post field directly. The character indicator uses a 280 character standard post target and counts URLs at their shortened length. Longer text may need shortening before you publish.

ControlWhat it changes
Headline / Supporting lineThe copy drawn on the image.
LayoutBrand editorial, Token spotlight or Statement. Business metric is available when the post has a metric.
PaletteProject brand, Mint, Blue, Violet, Ember or Night.
Background / Text / AccentIndividual colors for the artwork.
SizeLandscape at 2400 × 1350 or square at 2400 × 2400.

Download and publish

Holders can adapt available drafts into community posts. Replace any founder or team voice with your own, and avoid implying that your post is an official announcement.

  1. Choose Download PNG to export the image at full resolution.
  2. Choose Copy post or Open X for the text. Open X opens a composer; it does not publish.
  3. Attach the downloaded PNG in X, verify the active account, review both text and image, and publish there.

Use Tell the agent what to change and Write again for a new direction, such as “focus on the product release.” Review the new output before using it. If artwork cannot load, a ticker may replace it; reload the artwork before exporting if you need the logo.

WEB APP AGENTS

Outreach agent

Find relevant people and prepare a specific, evidence based message.

Start with the target cards

Open Things to do → Outreach agent. The agent uses available Reach data to find accounts connected to the coin or its market. If the owner’s identity lookup is needed, the empty state offers Sign once.

Targets can include current holders, past holders, followers of known holders, traders, related project creators, topic matches and accounts discovered through KOLs. Cards label the relationship and show the fact behind the suggestion. The current agent run returns up to 25 targets, not an exhaustive directory export.

Review the reason and the message

  1. Read the relationship label and observed fact. For example, the card may show the person’s holdings, a past position or an overlap with another token.
  2. Open the account or KOLs profile to assess current relevance. An inferred connection is not proof of interest or consent.
  3. Edit the draft to make one relevant ask. Keep the factual claim tied to its evidence, and remove anything that is stale or unsuitable.

Copy, DM or follow

Copy copies the edited draft. DM on X opens a message composer when a recipient ID is available, or the profile otherwise. Copy the draft and finish the message in X. Follow opens X’s follow flow. None of these buttons proves delivery.

If no candidates appear

Check token access, owner verification and the Reach data source. Review the “Needs” message before refreshing. Write again requests a new set from available context; it does not create missing identity evidence. A template label means the card uses fallback copy.

WEB APP AGENTS

Mentions agent

Review recent X mentions with a draft reply beside each post.

What the agent looks for

Open Things to do → Mentions agent. It reads available mentions of the token’s ticker or contract from the last day, with newest observations first. Adding the project’s X handle in Project info helps identify the account; contract search can still work without one.

Each card includes the author, original post text, available follower count and time, plus an editable reply. The agent excludes mentions already marked replied in its web records and limits a run to 25 targets. Provider coverage is not a complete view of X.

Reply to the actual post

  1. Read the original mention and open its context if needed. Confirm it concerns this contract rather than another token using the same ticker.
  2. Edit the draft to answer the question, acknowledge feedback or add a useful fact. Avoid treating every mention as an invitation to promote.
  3. Use Copy or Reply. Reply opens X with the target post and edited text. Complete and verify the reply there.

Freshness and missing results

X collection is designed to refresh on a roughly ten minute cadence, while agent outputs can be cached separately. Check timestamps. Write again reruns the drafting step against available data; it does not guarantee that the external provider has new posts.

An empty card explains whether it needs X access or data. If provider reads are paused, preserve that distinction instead of reporting that nobody mentioned the project.

WEB APP AGENTS

Whale watch

Inspect large observed buys and sells, then decide whether a follow up is useful.

Read the movement cards

Open Things to do → Whale watch. The agent uses available holder movement data for the selected window and ranks movements by dollar size. A wallet appearing on both the buy and sell sides is shown as an in and out move.

CardAvailable evidence
SellObserved dollars sold, supply percentage sold, remaining holdings and time.
BuyObserved dollars bought, current supply percentage and time.
In and outBoth buy and sell amounts with the current holding when available.

Understand identity and coverage

The card links a known account when Garp has an available wallet association. Otherwise it links the wallet’s explorer page. Absence of an X identity is not proof that the wallet has no public owner.

Use a draft appropriately

Known accounts can have an editable message, Copy, DM on X and Follow. Unnamed wallets have a Wallet link. A sell draft asks for feedback; a buy draft can welcome someone with a relevant fact. Review tone and evidence before choosing to contact anyone.

The run includes up to 25 targets. It is a sampled operating view, not a complete wallet history or an explanation of a trader’s motives. Use Write again to refresh the draft set when useful.

Related views

WEB APP AGENTS

GEO agent

Prepare useful material for places where people and AI assistants discover projects.

Open the GEO agent

Open Things to do → GEO agent. GEO means generative engine optimization: making clear, attributable project information available for discovery. The agent uses the project brief and available website audit to prepare content and recommendations.

The GEO agent drafts the work. The separate AI visibility panel measures available engine responses. A suggested post or a passing site check does not guarantee a citation.

What you receive

SectionHow to use it
Reddit postsSuggested subreddit, title, body and a reason for the angle.
Be where the engines readPlaces to improve project information, with a concrete task and destination when available.
Fix on the siteRelevant website audit issues that affect AI readiness.
Questions you should be the answer toBuyer questions to answer with clear, sourced information.

Review and publish the draft

  1. Check that the suggested community exists and read its current rules. An agent recommendation does not mean a post is permitted.
  2. Review the title and body for that audience. Verify product claims and contract details and disclose the team’s role where appropriate.
  3. Copy the text or choose Post on Reddit. Edit the title and body in the destination composer and complete the post there after review.
  4. Use Open the AI panel to inspect the citation tracker and follow up on the site fix list.

Write again refreshes the plan. “Built from templates” means the displayed plan is a fallback, not a custom model generated assessment.

Useful supporting material

Recommendations can include a factual questions page, consistent project profiles, structured data, a GitHub README, an X bio or pinned post, and an llms.txt file. Garp can provide a hosted project file and a download; publishing it on your domain is a separate action.

WEB APP AGENTS

Website and search readiness

Turn the website audit into a clear list of changes to make on your site.

Find the audit

Add the correct website in Project info. Open Analytics → Site, or choose Website → Open the Site panel from Things to do when that row is available.

The panel reads the public site and reports readiness checks, source details and fixes. The Website row surfaces up to five outstanding search related checks with a summary score. No website or a failed fetch is a setup or retrieval issue, not a successful audit.

Work through the checks

Read each failed check’s explanation and prescribed fix. The audit covers available page metadata, crawl and discovery signals, project identity and related readiness signals. Use the actual returned checks to decide what to change; a score alone does not identify the problem.

Make the changes in your website’s own code or publishing system, then refresh the audit. Garp’s Website row does not deploy those changes to your domain. A passing readiness score is not a guarantee of search ranking or traffic.

Measure traffic and product usage

Connected Google Analytics and Search Console can add traffic and search reports. Supabase can add table counts and growth for the app behind the token. These are different sources and populations: website visitors, registered accounts and database rows are not interchangeable.

Read the selected date range and report timestamp. If the connection exists but access has expired, reconnect or refresh the authorization through the source controls.

Publish a project llms.txt file

The AI site map (llms.txt) sheet shows a hosted Garp URL and offers Copy the file and Download llms.txt. The hosted copy uses project information; it does not place a file on your own domain.

Use the sheet’s deployment examples to serve the file at your domain root or route that path to the hosted copy. Keep the contract and factual description current. This is a readable project resource, not a promise that every engine will use it.

WEB APP AGENTS

AI visibility and citation tracker

Inspect what configured AI engines actually say about your project.

Open the AI panel

Open Analytics → AI, or use Open the AI panel in the GEO agent. The panel combines a visibility grade, component scores, engine readiness, buyer prompts and a prioritized fix list.

Read the denominator and last checked time with the score. Engine readiness and actual citation answers are different signals. An engine that is not connected or not asked is not an observed failure to name the project.

Run and manage buyer questions

  1. Connect the eligible owner wallet. Choose Sign and run the check or Run the check when available.
  2. Wait for the progress count to finish. A check can take minutes; the panel polls the running state.
  3. Expand a buyer prompt to inspect each engine’s answer and available sources.
  4. Use Re-check for a later measurement. Rewrite the prompts rebuilds the buyer questions. Add your own question with Ask; custom questions can be removed.

Engine checks require configured providers. Disabled or unconfigured controls do not mean the token failed a check. Signing authorizes the relevant operation, not arbitrary changes to your project.

Interpret each answer

The tracker distinguishes a named project, no relevant mention, a different token with the same name, a different contract, a “cannot find it” response and an engine not asked. Open the answer text to inspect the reasoning and source material instead of relying only on the icon.

Branded prompts name the project in the question. Unbranded discovery prompts ask about a problem or category without naming it. Being recognized by name and being recommended during discovery measure different things.

Use the fix list

Open a fix to see its impact, explanation and where to act. The panel distinguishes material Garp can prepare from changes you make yourself. Website facts, contract consistency and useful public answers provide concrete work to complete before checking again.

WEB APP AGENTS

Reach and holder insights

Understand who holds the coin and which observed relationships could matter.

Open Reach and holder data

Open the Reach panel for named account suggestions and Analytics → Holders for available holder data. Protected identity enrichment can require the owner’s wallet signature. Token access and chain coverage can also affect the result.

Reach provides the evidence used by the Outreach agent. It can combine observed holders and past holders with followers, similar traders, creator overlap and KOLs candidates. Each group explains a different relationship; do not treat them as one equally qualified audience.

Read context before ranking

Inspect available holdings, time held, exited positions, overlap and relationship reasons. Holder concentration and trading observations describe a window and an indexed sample. A named wallet association is available evidence, not a complete identity verification service.

A missing holder report is unknown data. An unlabelled wallet is not necessarily a new person, and a follow link is not proof that an introduction can be arranged.

Maintain a useful contact workflow

Review candidates before opening a profile or composing a message. Use the available owner contact controls to record actual progress and avoid repeated outreach. A browser action that opens X does not independently verify delivery.

Use KOLs for broader discovery

Open KOLs to inspect a public account’s available posts, relationships and activity. This is useful when a Reach card needs more context, or when you want to research an audience before choosing a token. Keep evidence freshness visible in any shortlist.

WEB APP AGENTS

Ask Garp

Ask practical questions using the token’s available live context.

Start a conversation

Open your token workspace and find Ask Garp. Suggested questions include what to post today, who to bring in, how the fee rate compares and whether supply locking deserves consideration. You can also write a more specific question.

Example question
What should we work on today? Use the available project facts,
show which observations support the answer, and give me three actions.

Supply the outcome you care about and any time constraint. The assistant uses available token, market and project context; missing sources should stay explicit.

Make the answer actionable

Ask follow up questions in the same conversation to refine a draft or investigate evidence. Confirm that a suggested action matches the product and current data before acting. A chat response proposing a post or a wallet action has not performed it.

Use Content agent for image exports, Reach for the underlying account evidence, and the Coin or Analytics panels to inspect the corresponding figures.

Quotas and unavailable context

Chat has daily limits and can return remaining quota or a fallback response. The configured server defaults are 40 requests per IP per day with a shared service cap; deployment settings can change them. If a limit is reached, use the reset information in the response.

A missing provider or missing project connection can reduce the context or response quality. Do not treat a fallback as proof that an external source was checked.

WEB APP AGENTS

Sources and integrations

Give the agents current product information and the sources they need.

Project info, X and GitHub

Use Project info to maintain the description, website, X handle and other supported links. The owner signs a profile publish. Supplying a URL is not the same as a successful fetch; check the content agent’s Sources cards afterward.

Website text supplies product context. X can supply recent project posts and social observations. GitHub can supply repository facts and recent commit activity. These links do not authorize the agents to publish to X or edit your repository.

Google Analytics and Search Console

  1. From the token’s connection controls, choose Google Analytics when it is available and connect using the owner flow.
  2. Complete Google authorization and select the available Analytics property or Search Console site.
  3. Open Analytics → Site to read reports and select the available date range.
  4. Refresh the report as needed. Use the disconnect control if you no longer want that connection.

Provider configuration and account permissions determine which properties are visible. Public connection status is distinct from private reports. Linking a token to a site does not create an Analytics property or verify a Search Console domain.

Supabase app data

Use the owner’s Connect Supabase flow with the project URL and a key permitted to read the intended data. The interface accepts an anon key where its access rules permit the needed reads. Enter credentials only in the connection form, never in public project text or drafts.

The app shows available table counts and growth, with preview and content selection controls. Select deliberately which tables can inform content. Garp’s content agent can read selected table counts and sampled recent rows; avoid enabling data that should not inform public copy. Review generated claims before publishing.

Garp’s integration performs reads and seals the supplied key on the server. The key’s own privileges can be broader than the operations Garp performs. A connected database does not mean every table is readable or selected.

Missing, stale or disconnected sources

Follow the source’s status and error message. Reauthorize expired provider access, correct a website link, or adjust allowed table access through the appropriate service. Regenerating content cannot repair an unavailable source by itself.

WEB APP AGENTS

Fees, supply locks and project info

The owner actions shown alongside the agents in Things to do.

Fees and payouts

Expand Fees or open the fee analytics view to inspect the available payout figures. Lifetime paid out, fees earned during the selected window and currently claimable funds are different measurements. Check the asset, chain, launchpad and estimate labels.

Controls vary by launchpad. The app can show automatic payout status, a supported claim action, or a link such as Claim on pump.fun. A pump.fun creator vault can include multiple coins from the same creator. Do not interpret its full balance as earnings for one token.

A pending fee handover has its own recipient and timing. Review those details and wallet permissions before using Confirm fee handover or Cancel.

Token lock kit

On Robinhood Chain, open a token workspace and find Token lock kit. Any holder can lock their own tokens. The feature becomes available when the Garp Locker is activated on that network; Solana locks are not supported.

Lock tokens lets you enter an exact amount or choose a percentage of your wallet balance. Choose an all-at-once release or linear vesting after the start date. Dates are shown at 12:00 UTC. Review the amount, token and dates, approve the allowance if needed, then confirm the lock in your wallet. The confirmation reports the amount actually received by the contract and links to its transaction.

After confirmation, Garp prepares a custom share card with the Garp logo, token, percentage of total supply, amount and release schedule. Choose Share on X, Copy link or Download image. The public receipt link includes a large image preview. The percentage is the amount received by the locker divided by total supply at the creation block, rounded down; it is not the percentage of your wallet balance. The card records the original lock, so later claims, top-ups, transfers, extensions and supply changes do not rewrite it. Open the token page for current lock status. Existing indexed locks with a creation transaction offer Share original lock.

Add tokens keeps the original schedule, so the already-vested portion of a top-up is immediately claimable. Extend moves dates later and may restrict unclaimed tokens again. Claim sends available tokens to the lock owner. Transfer lock gives the recipient control of the lock without changing release dates; Garp cannot reverse the transfer.

The public token page lists creator and holder locks separately, with owners, release dates and a Blockscout link. Vested tokens awaiting a claim are not counted as still time locked. If indexing is delayed, the page labels the last recorded schedules instead of asserting a current locked balance. A lock does not remove minting, freezing or other powers in the token contract.

Publish official information

Use Project info to edit the description, art and supported links. Review the full profile before choosing Sign and publish or Publish update. The owner signature authorizes the publish.

The resulting profile feeds Garp and the public Token API. Buying Garp service credits does not give the buyer permission to edit a token’s official profile. See the API guide for field limits, source precedence and revision rules.

Project information

TOKEN API

One token

Read one complete token document. Public JSON, no API key required.

Request and reference

Pass a contract address (Robinhood Chain) or a mint (Solana). The chain is read off the address. Coins Garp indexes answer from memory; a Robinhood Chain coin Garp has never seen is read straight off the chain, which takes a few seconds the first time. Add ?deep=0 to skip that and get the name, symbol and supply only.

GET/api/v1/token/{address}
curl https://www.usegarp.com/api/v1/token/0x1cdb289befdfac8af945a288bcdccc382cb34d32
{
  "schemaVersion": "1.0",
  "chainId": "robinhood",
  "chain": { "id": "robinhood", "name": "Robinhood Chain", "evmChainId": 4663 },
  "address": "0x1cdb289befdfac8af945a288bcdccc382cb34d32",
  "name": "X Link", "symbol": "XL", "decimals": 18,
  "logo": "https://gateway.pinata.cloud/ipfs/QmUHqo…",
  "banner": null,
  "description": "The first protocol that links on-chain fees to X Money. …",
  "links": [
    { "type": "website", "label": "Website", "url": "https://xl.money" },
    { "type": "twitter", "label": "@xLinkMoney", "url": "https://x.com/xLinkMoney" }
  ],
  "launchpad": "pons-v2", "launchedAt": "2026-09-13T17:57:54.000Z", "graduated": true,
  "deployer": "0x61bf…bd91", "feeRecipient": "0x2af4…e449", "owner": "0x2af4…e449",
  "market": {
    "priceUsd": 0.00108, "marketCapUsd": 1082018, "volumeUsd": 1256523.18, "volumeWindowHours": 24,
    "priceChangePct": 24.3, "swaps": 6235, "buys": 3468, "sells": 2767, "makers": 72,
    "totalSupply": 1000000000, "circulating": 1000000000, "lastTradeAt": "2026-09-13T23:20:04.000Z",
    "pool": { "kind": "uniswap-v4", "poolId": "0x713a…d503", "address": null, "quote": { "symbol": "USDG", "address": "0x5fc5…d168" } }
  },
  "fees": { "creatorEarnedUsd": 33384.42, "claimedUsd": 0, "totalEarnedUsd": 33384.42, "estimated": false, "windowHours": 24 },
  "profile": { "published": false, "revision": 0, "updatedAt": null, "by": null, "ownerVerified": false, "fields": [] },
  "urls": { "garp": "…/board#t/0x1cdb…4d32", "explorer": "https://robinhoodchain.blockscout.com/token/0x1cdb…4d32", "api": "…/api/v1/token/0x1cdb…4d32" },
  "indexed": true, "servedAt": "2026-09-13T23:21:22.078Z"
}
Where the information comes from. Field by field, the best source wins: what the project published here and signed with its owner wallet, then links the owner signed on Garp before, then the token's own metadata on chain and what Garp indexed. profile.fields lists the fields that came from the project itself, and profile.ownerVerified says whether the wallet that signed them is the deployer, the fee recipient, or the wallet the coin was handed to.
TOKEN API

Batch and search

Look up multiple indexed tokens or search by name and symbol.

Request and reference

Up to 30 addresses in one call. Batch answers only for coins Garp indexes; anything else comes back with an error row pointing at the single-token route, which does the chain lookup.

GET/api/v1/tokens?addresses=0x…,0x…,So1…
{ "count": 2, "tokens": [ { …token… }, { "address": "0x…", "chainId": "robinhood", "error": "not indexed; ask /api/v1/token/{address} for a chain lookup" } ] }

Search by name or symbol across the indexed coins, ranked by volume. Two characters minimum, twenty results.

GET/api/v1/search?q=xl
{ "query": "xl", "count": 1, "tokens": [ { "chainId": "robinhood", "address": "0x1cdb…4d32", "name": "X Link", "symbol": "XL", "logo": "…", "launchpad": "pons-v2", "priceUsd": 0.00108, "marketCapUsd": 1082018, "volumeUsd": 1256523.18, "url": "…/api/v1/token/0x1cdb…4d32" } ] }
TOKEN API

What changed

Track profile updates and read signed revision history.

Request and reference

Every profile a project has published, newest first. Poll it with since set to the newest updatedAt you have seen and you get only what changed after that, which is how a listing bot keeps its own copy current. since takes an ISO timestamp or unix seconds; limit goes up to 500.

GET/api/v1/profiles/latest?since=2026-09-13T00:00:00Z&limit=100
{
  "count": 1, "since": "2026-09-13T00:00:00.000Z",
  "profiles": [ {
    "chainId": "robinhood", "address": "0x1cdb…4d32", "name": "X Link", "symbol": "XL",
    "revision": 2, "updatedAt": "2026-09-13T23:23:26.000Z", "by": "0x2af4…e449", "ownerVerified": true,
    "logo": "…", "banner": "…", "description": "…",
    "links": [ { "type": "website", "label": "Website", "url": "https://xl.money" }, { "type": "telegram", "label": "Telegram", "url": "https://t.me/xlinkmoney" } ],
    "url": "…/api/v1/token/0x1cdb…4d32"
  } ],
  "next": { "since": "2026-09-13T23:23:26.000Z" }
}

One coin's published profile, and every revision it has ever had, each with the signature that vouched for it.

GET/api/v1/token/{address}/profile
GET/api/v1/token/{address}/history
TOKEN API

Publish token info

Publish official token information with an owner wallet signature.

Request and reference

A project publishes its own links, description, logo and banner here. Every publish is signed by the token owner wallet, so nobody can put words in a project's mouth. Open the token’s workspace and use Token info to prepare and sign an update.

Garp AI work is funded by the service credits and plans shown on the pricing page. Public token tracking remains available without an AI plan.

1. Prepare: get the exact message to sign

Send the fields you want to publish. The server cleans them (handles become handles, links get their scheme, the order is fixed) and hands back the cleaned profile, a timestamp, and the message. Sign that message as-is.

POST/api/v1/token/{address}/profile/prepare
curl -X POST https://www.usegarp.com/api/v1/token/0x…/profile/prepare \
  -H 'content-type: application/json' \
  -d '{ "profile": { "description": "X Link links on-chain fees to X Money.", "website": "xl.money", "twitter": "@xLinkMoney", "telegram": "t.me/xlinkmoney", "links": [ { "label": "Docs", "url": "docs.xl.money" } ] } }'

{
  "at": "2026-09-13T23:22:13.792Z",
  "profile": { "description": "X Link links on-chain fees to X Money.", "website": "https://xl.money", "twitter": "xLinkMoney", "telegram": "xlinkmoney", "links": [ { "label": "Docs", "url": "https://docs.xl.money" } ] },
  "message": "Garp: update token info for 0x…\n2026-09-13T23:22:13.792Z\n{\"description\":\"X Link links on-chain fees to X Money.\",\"website\":\"https://xl.money\",…}",
  "expiresInSeconds": 600
}

The message is three lines: Garp: update token info for {address}, the timestamp, and the cleaned profile as compact JSON in the field order below. On Robinhood Chain sign it as a personal message (EIP-191, what personal_sign and ethers' signMessage produce). On Solana sign the UTF-8 bytes with the wallet's ed25519 key and base58-encode the signature, which is what signMessage in Phantom, Solflare and Backpack does.

2. Publish

POST/api/v1/token/{address}/profile
curl -X POST https://www.usegarp.com/api/v1/token/0x…/profile \
  -H 'content-type: application/json' \
  -d '{ "signer": "0x2af4…e449", "signature": "0x…", "at": "2026-09-13T23:22:13.792Z", "profile": { …exactly what prepare returned… } }'

{ "ok": true, "revision": 1, "updatedAt": "2026-09-13T23:23:26.000Z", "ownerVerified": true, "token": { …the full token document, as everyone now reads it… } }
Who can sign. The coin's deployer, its fee recipient, or the wallet it was handed to in a community takeover on Garp. If ownership cannot be verified, publishing is rejected. A publish replaces the whole profile; leave a field out to fall back to the token's on-chain metadata, or send an empty string to explicitly remove it. The timestamp has to be inside ten minutes and newer than the last revision, so a signed body cannot be replayed.
TOKEN API

Profile fields

Accepted fields, formats and limits for official token profiles.

Request and reference

All optional, at least one required. This is also the order they appear in the signed message.

FieldAcceptsPublished as
descriptionUp to 1,000 characters, line breaks keptdescription
logohttps or ipfs URL, up to 300 characterslogo, replacing the launch art
bannerhttps or ipfs URLbanner
websiteURL, scheme optionala website link
twitter@handle, handle, or an x.com / twitter.com linka twitter link, https://x.com/handle
telegram@group or a t.me link, invite links includeda telegram link, https://t.me/…
discorddiscord.gg or discord.com/invite linka discord link
githubowner, owner/repo, or a github.com linka github link
linksUp to 6 of { "label", "url" }, labels up to 32 charactersother links, in order
TOKEN API

Response fields

Understand token documents, source precedence and market windows.

Request and reference

FieldMeaning
chainIdrobinhood or solana. chain.evmChainId is 4663 on Robinhood Chain.
addressThe contract address, lowercased, or the Solana mint as written.
links[]{ type, label, url } rows. type is one of website, twitter, telegram, discord, github, other.
launchpadpons-v2, pons-v1, pools-trade, bags-v1, bags-v2, hoodmint, quiver, hookos, pumpfun, stonkfun, or null for a coin paired by hand.
ownerThe wallet Garp treats as the coin's owner: the fee recipient or deployer, or the wallet it was handed to.
marketPrice, market cap and change are live. volumeUsd, swaps, buys, sells and makers cover the last volumeWindowHours. pool names the venue: a Uniswap v4 pool id, a v3 pool, a launch curve, or a Raydium / PumpSwap pool on Solana, with the quote asset.
feesWhat the coin paid its creator in the window and all time. estimated: true means the figure is derived from volume and the launchpad's fee rule rather than read off each trade.
profileWhether the project has published, which fields came from it, the revision, and whether the signing wallet was verified as the owner.
accessLegacy token access metadata. Garp AI plans and service credits are listed separately on Pricing.
indexedfalse for a coin read off the chain on request rather than followed by Garp's indexer. Market data for those is read from the pool's own swaps over the last day.
Responses carry cache-control: public, max-age=5: a token document is at most a few seconds old. Numbers are plain JSON numbers, timestamps are ISO 8601 in UTC, and null means not known rather than zero.
TOKEN API

Errors

HTTP status codes and actionable API error responses.

Request and reference

Every error is JSON with an error sentence a person can read.

StatusWhen
400Not an address or a mint, or a profile field that does not clean up: the message names the field.
401The signature does not match the signer, or at is missing or older than ten minutes.
403The signer is not the coin's owner wallet. The body lists the wallets that are.
404No token at that address, or no profile published yet.
409A newer revision is already published; sign again with a fresh at.
429Over the limit: 600 reads, 30 chain lookups or 20 publishes a minute per IP.
Questions, a field you need, or a listing you want to wire up: reach the founder.
Garp documentation Reference verified September 23, 2026