Introducing the BaseFriend Builder Grant
Build a Farcaster Mini App with creator keys, staking or Cheers tipping. The monthly Builder Grant rewards pool totals *1,250,000 CHEERS*.
A club might want a place to discover its members’ favorite creator markets. A supporter might want one screen to see which keys are staked and when they unlock. A community might want a leaderboard for the people who keep tipping others. We opened BaseFriend’s APIs so you can build those experiences and apply for a grant with a live app.\
What you can build
Start with a feature your community would use. Here are three places to begin:
- *Creator and club discovery.* Build a directory with profile images, key supply and indicative prices. Use GET /markets with type=creator or type=channel for clubs, pass q to search, and use GET /market?id=… for a detail screen.
- *A key portfolio or staking companion.* Use GET /wallet?wallet=… to show free and staked creator or club keys, indexed unlocks and reward estimates. Follow nextCursor for more positions. You can add buy, sell, stake and unstake flows through the user’s wallet.
- **A Cheers dashboard.** Use GET /summary for the tipping program and tip totals, GET /account?fid=… for an account’s recorded allowance and recent tips, and GET /leaderboard for top senders or receivers. Label projections and pending amounts clearly. [Tipping API specification](https://basefriend.tech/tipping-api-v1.openapi.json)
The Market API runs on Base Mainnet, chain ID 8453. Creator and club keys are whole units. The current market payment asset is $KEY. Use GET /config to retrieve the contract, ABI, supported actions and current settlement details as your app loads. Preserve exact numeric strings for key amounts, token IDs and payment amounts. [Market API specification](https://basefriend.tech/basefriend-builder-api-v1.openapi.json)\
\
Make your first request and get an app key
You can prototype with public reads straight away. This request returns up to five creator markets:
curl -fsS --max-time 15 \
'https://basefriend.tech/api/public/basefriend/v1/markets?type=creator&limit=5'
Read data.items for the results and data.nextCursor for pagination. Use asOf and expiresAt to show data freshness. For trade prices, request a wallet-specific quote.
To attribute activity to your app, open *GRANT* in BaseFriend, connect and sign in, and submit your app. Under *APP LEADERBOARD*, open *API ACCESS & ACTIVITY* on that application and create a key. Copy it into a backend secret such as BASEFRIEND_APP_API_KEY. BaseFriend shows the full key once, and the same key works for market and tipping requests. The submitting wallet can rotate or revoke it from that panel.
curl -sS -i --max-time 15 \
-H "Authorization: Bearer ${BASEFRIEND_APP_API_KEY:?Set this on your backend}" \
'https://basefriend.tech/api/public/tipping/v1/summary'
Look for X-BaseFriend-Usage: recorded to confirm the request was recorded. Send the bearer header from your backend and keep the key out of your Mini App bundle, URLs and public repositories. The two APIs share **30 requests per minute per IP**, including keyed requests. Cache public reads within their stated lifetime and honor Retry-After on rate limits or temporary outages. [BaseFriend builder guide](https://basefriend.tech/basefriend-builder-guide.html)\
Add a real wallet action
The action flow is *quote → prepare → review and sign → confirm*. For a trade, get a fresh quote for the connected wallet and requested amount. A quote lasts up to 10 seconds. POST /prepare returns an unsigned call and, when needed, a token approval. The connected wallet signs and sends the reviewed transaction.
Here’s a backend example that prepares a one-key buy and reports a submitted transaction. Pass the real market ID, the connected wallet and the slippage tolerance the user selected, from 0 to 500 basis points.
const api = "https://basefriend.tech/api/public/basefriend/v1";
const appKey = process.env.BASEFRIEND_APP_API_KEY;
if (!appKey) throw new Error("Set BASEFRIEND_APP_API_KEY on your backend.");
async function market(path, body) {
const headers = { Authorization: `Bearer ${appKey}` };
const hasBody = body !== undefined;
if (hasBody) headers["Content-Type"] = "application/json";
const response = await fetch(`${api}/${path}`, {
method: hasBody ? "POST" : "GET",
headers,
body: hasBody ? JSON.stringify(body) : undefined,
signal: AbortSignal.timeout(15_000),
});
const result = await response.json().catch(() => ({}));
if (!response.ok) {
throw new Error(result.error?.code ?? `HTTP ${response.status}`);
}
return result.data;
}
export async function prepareOneKeyBuy({ entityId, wallet, slippageBps }) {
const amount = "1";
const query = new URLSearchParams({ entityId, wallet, side: "buy", amount });
const quote = await market(`quote?${query}`);
return market("prepare", {
action: "buy",
entityId,
wallet,
amount,
referenceAmount: quote.reserveAmount,
slippageBps,
maxGenesisDebtPayment: "0",
settlementIdentity: quote.settlementIdentity,
});
}
export function confirmAction(intentId, txHash) {
return market("confirm", { intentId, txHash });
}
\1. *Review the prepared call.* Check the chain, contract, caller, payment asset, amounts, fees and slippage. If the call requires an approval, show and simulate the exact approval, get the user’s confirmation, wait for its receipt, then refresh the quote and preparation.
\2. *Get the user’s signature.* Simulate the market call from the same wallet and show it for approval. Save the transaction hash and prepared.activity.intentId, using the intent’s executeBefore and reportBefore deadlines.
\3. *Report the trade.* Use your app’s active key to POST /confirm with { intentId, txHash }. On 202 or data.status: "pending", wait for the indicated retry interval and retry the confirmation with the same hash. Attribution in v1 verifies a matching direct market transaction on Base after finality. Wrapped Safe, multicall and account-abstraction transactions are outside that attribution scope.
Stake and unstake use { action, wallet, entityId, amount } with /prepare. Use the market’s live unlock rules. The same API also prepares staking reward and creator fee claims. Genesis claims follow the existing creator and club approval flow. [Wallet action schemas](https://basefriend.tech/basefriend-builder-api-v1.openapi.json)
How activity points work
The *API ACCESS & ACTIVITY* panel shows private reports for the last *7, 30 or 90 UTC days*. You and Chef can see requests by day and endpoint, verified actions and provisional activity points. Use the report to understand how people use your integration and include evidence of the outcomes in your application.
Successful recorded requests with a valid app key can contribute points. Each app can earn up to *100 points a day from reads and preparation* and *500 points a day overall*, measured in UTC.
| Successful read | Points |
|---|---|
| Configuration | 0 |
| Browse creators or clubs, or search markets | 1 |
| Market details | 2 |
| Wallet holdings and staking | 3 |
| Buy quote | 2 |
| Sell quote | 1 |
| Tipping summary | 1 |
| Tipping account | 3 |
| Tipping sender or receiver leaderboard | 1 |
| Market action | Successful prepare |
| - | - |
| Buy creator or club keys | 2 |
| Sell creator or club keys | 0 |
| Stake keys | 2 |
| Unstake keys | 0 |
| Claim staking rewards | 0 |
| Claim creator or club fees | 0 |
| Claim creator or club Genesis | 0 |
A transaction scores once. A qualifying buy and a qualifying stake each score at most once per wallet and market per UTC day across apps. An eligible Genesis claim scores once per market. Reward and fee claims must pay a positive amount, and a batch staking reward claim earns 5 points total. Anonymous traffic, errors, HEAD, OPTIONS and 304 responses earn zero points. [Activity scoring rules](https://basefriend.tech/basefriend-builder-guide.html#grants)
The activity report informs Chef’s review. Chef assigns a *separate grant score* to approved apps. Grant scores and activity points are separate from App Points and token balances.
Apply for the monthly grant
Each month, Chef selects winners after reviewing app quality, usefulness and evidence of real activity. Here are the monthly award tiers.
| Placement | Monthly award |
|---|---|
| 1st | 500,000 CHEERS |
| 2nd | 300,000 CHEERS |
| 3rd | 100,000 CHEERS |
| 4th–10th | 50,000 CHEERS each |
Open *GRANT* and sign in with the wallet you want to manage the application. Submit:
- Your app name, a public HTTPS link to the live app, and your Farcaster handle or contact.
- The BaseFriend feature you integrated and who it helps.
- A short account of what shipped and how it was used, including the dates covered.
- Up to five evidence links, such as a demo cast, public analytics or relevant transaction receipts. You can also add a source code or build log link.
After submitting, use *APP LEADERBOARD* to follow review status, feedback and any grant score. Chef and the submitting wallet can see the application and feedback. Editing an application puts it back in review and resets its current grant score.
Pick one workflow worth improving for your community, ship it, and show us what people did with it. **[Open BaseFriend](https://basefriend.tech/) and tap GRANT.**