You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/ai-agents/setup/agent-builder-codes.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -109,5 +109,5 @@ No authentication required.
109
109
Returns the builder code for the given wallet. The same wallet address always returns the same code and is safe to call multiple times.
110
110
111
111
## Further reading
112
-
-[Builder Codes Overview](/base-chain/builder-codes/builder-codes) - What Builder Codes are, how ERC-8021 attribution works, and FAQs on gas, identity, and wallet support
113
-
-[Builder Codes for Agent Developers](/base-chain/builder-codes/agent-developers) - API reference, skill reference, and overview
112
+
-[Builder Codes Overview](/apps/builder-codes/builder-codes) - What Builder Codes are, how ERC-8021 attribution works, and FAQs on gas, identity, and wallet support
113
+
-[Builder Codes for Agent Developers](/apps/builder-codes/agent-developers) - API reference, skill reference, and overview
| FID-based notifications via Neynar | Wallet-address notifications via Base.dev notifications API *(coming soon)*|
24
24
| Farcaster SDK for auth and actions | wagmi + viem + Sign-In with Ethereum (SIWE) |
25
-
| Search and discovery via Farcaster | Base.dev app metadata + [builder codes](https://docs.base.org/base-chain/builder-codes/builder-codes)|
25
+
| Search and discovery via Farcaster | Base.dev app metadata + [builder codes](https://docs.base.org/apps/builder-codes/builder-codes)|
26
26
27
27
---
28
28
@@ -173,7 +173,7 @@ Your app uses the Farcaster SDK. The migration replaces Farcaster-specific auth,
173
173
</Step>
174
174
175
175
<Steptitle="Register on Base.dev">
176
-
If you haven't registered yet, create a project at [Base.dev](https://www.base.dev) and complete your app metadata: name, icon, tagline, description, screenshots, category, primary URL, and [builder code](/base-chain/builder-codes/builder-codes). Already registered apps do not need to re-register or update metadata.
176
+
If you haven't registered yet, create a project at [Base.dev](https://www.base.dev) and complete your app metadata: name, icon, tagline, description, screenshots, category, primary URL, and [builder code](/apps/builder-codes/builder-codes). Already registered apps do not need to re-register or update metadata.
177
177
</Step>
178
178
</Steps>
179
179
@@ -193,7 +193,7 @@ Your app is already a standard web app. You're mostly done — just verify your
193
193
</Step>
194
194
195
195
<Steptitle="Register on Base.dev">
196
-
If you haven't registered yet, create a project at [Base.dev](https://www.base.dev) and complete your app metadata: name, icon, tagline, description, screenshots, category, primary URL, and [builder code](/base-chain/builder-codes/builder-codes). Already registered apps do not need to re-register or update metadata.
196
+
If you haven't registered yet, create a project at [Base.dev](https://www.base.dev) and complete your app metadata: name, icon, tagline, description, screenshots, category, primary URL, and [builder code](/apps/builder-codes/builder-codes). Already registered apps do not need to re-register or update metadata.
197
197
</Step>
198
198
199
199
<Steptitle="Integrate notifications (optional)">
@@ -246,7 +246,7 @@ Before considering your app migrated, verify the following:
246
246
</Step>
247
247
248
248
<Steptitle="Register and complete Base.dev metadata">
249
-
Project is registered on [Base.dev](https://www.base.dev) with primary URL set. Name, icon, tagline, screenshots, category, description, and [builder code](/base-chain/builder-codes/builder-codes) are all filled in.
249
+
Project is registered on [Base.dev](https://www.base.dev) with primary URL set. Name, icon, tagline, screenshots, category, description, and [builder code](/apps/builder-codes/builder-codes) are all filled in.
250
250
</Step>
251
251
252
252
<Steptitle="Notifications use Base.dev API (if applicable)">
Copy file name to clipboardExpand all lines: docs/base-account/reference/core/capabilities/dataSuffix.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -103,7 +103,7 @@ When a wallet receives a `dataSuffix` capability, the suffix is appended to `use
103
103
104
104
### Builder Codes Attribution
105
105
106
-
The primary use case for `dataSuffix` is [Builder Codes](/base-chain/builder-codes/builder-codes) attribution. Builder Codes are unique identifiers that allow apps to receive attribution for onchain activity they generate.
106
+
The primary use case for `dataSuffix` is [Builder Codes](/apps/builder-codes/builder-codes) attribution. Builder Codes are unique identifiers that allow apps to receive attribution for onchain activity they generate.
107
107
108
108
```typescript
109
109
import { Attribution } from"ox/erc8021";
@@ -144,7 +144,7 @@ Register on [base.dev](https://base.dev) to get your Builder Code for proper att
144
144
3.**Keep suffixes small**: Larger suffixes increase gas costs
145
145
146
146
<Info>
147
-
For wallet developers implementing dataSuffix support, see the [For Wallet Developers](/base-chain/builder-codes/builder-codes#for-wallet-developers) section in the Builder Codes guide.
147
+
For wallet developers implementing dataSuffix support, see the [For Wallet Developers](/apps/builder-codes/builder-codes#for-wallet-developers) section in the Builder Codes guide.
0 commit comments