docs(llms): append .md to absolute internal docs URLs in llms-full shards; keep .txt links unchanged

Author: ericbrown99

docs/base-account/llms-full.txt

@@ -77,7 +77,7 @@ const { status } = await getPaymentStatus({ id })
 
 ## Quickstart (excerpts)
 
-Source: `https://docs.base.org/base-account/quickstart/web`
+Source: `https://docs.base.org/base-account/quickstart/web.md`
 
 Base Account lets you add a passkey‑secured ERC‑4337 smart account to your app, with sponsored gas, batch transactions, spend permissions, and sub‑accounts.
 
@@ -122,13 +122,13 @@ const result = await account.provider.request({
 Expected result: a single ERC‑4337 userOp executes both calls atomically. Combine with a paymaster to sponsor user gas.
 
 Additional sources:
-- `https://docs.base.org/base-account/quickstart/mobile-integration`
-- `https://docs.base.org/base-account/framework-integrations/wagmi/setup`
+- `https://docs.base.org/base-account/quickstart/mobile-integration.md`
+- `https://docs.base.org/base-account/framework-integrations/wagmi/setup.md`
 
 
 ## Key Concepts (excerpts)
 
-Source: `https://docs.base.org/base-account/overview/what-is-base-account`
+Source: `https://docs.base.org/base-account/overview/what-is-base-account.md`
 
 - Ownership model: A Base Account is owned by an EOA or another smart wallet. Ownership can be rotated via recovery flows, and sub‑accounts can be created for app‑scoped spend.
 - Recovery: Supports social/device delegates with threshold approval. Ownership only changes after quorum is met and verification passes.
@@ -139,31 +139,31 @@ Source: `https://docs.base.org/base-account/overview/what-is-base-account`
 - Security assumptions: Only configured owner(s) can authorize changes. Recovery requires meeting your policy’s threshold.
 
 Additional sources:
-- `https://docs.base.org/base-account/overview/architecture`
-- `https://docs.base.org/base-account/improve-ux/spend-permissions`
-- `https://docs.base.org/base-account/improve-ux/sponsor-gas/paymasters`
-- `https://docs.base.org/base-account/improve-ux/batch-transactions`
+- `https://docs.base.org/base-account/overview/architecture.md`
+- `https://docs.base.org/base-account/improve-ux/spend-permissions.md`
+- `https://docs.base.org/base-account/improve-ux/sponsor-gas/paymasters.md`
+- `https://docs.base.org/base-account/improve-ux/batch-transactions.md`
 
 
 ## API Reference (selected, pruned)
 
 Provider RPC methods (subset)
 
 - `wallet_sendCalls(params)` — Execute one or more calls in a single ERC‑4337 user operation. Returns a user operation hash.
-  - Source: `https://docs.base.org/base-account/reference/core/provider-rpc-methods/wallet_sendCalls`
+  - Source: `https://docs.base.org/base-account/reference/core/provider-rpc-methods/wallet_sendCalls.md`
 - `wallet_getCapabilities()` — Return wallet features and limits supported by the provider.
-  - Source: `https://docs.base.org/base-account/reference/core/provider-rpc-methods/request-overview`
+  - Source: `https://docs.base.org/base-account/reference/core/provider-rpc-methods/request-overview.md`
 
 SDK helpers (subset)
 
 - `createBaseAccount(options)` — Initialize SDK and get a configured provider and helpers
-  - Source: `https://docs.base.org/base-account/reference/core/createBaseAccount`
+  - Source: `https://docs.base.org/base-account/reference/core/createBaseAccount.md`
 - `getProvider()` — Access the EIP‑1193 provider wired to Base Account
-  - Source: `https://docs.base.org/base-account/reference/core/getProvider`
+  - Source: `https://docs.base.org/base-account/reference/core/getProvider.md`
 - `createSubAccount({ label })` — Create an app‑scoped sub‑account
-  - Source: `https://docs.base.org/base-account/reference/core/capabilities/overview`
+  - Source: `https://docs.base.org/base-account/reference/core/capabilities/overview.md`
 - `pay({ amount, to, testnet })` and `getPaymentStatus({ id })` — Base Pay helpers for USDC flows
-  - Source: `https://docs.base.org/base-account/guides/accept-payments`
+  - Source: `https://docs.base.org/base-account/guides/accept-payments.md`
 
 Minimal request example for `wallet_sendCalls`:
 
@@ -187,7 +187,7 @@ Minimal request example for `wallet_sendCalls`:
 
 Example: Authenticate user with SIWE + ERC‑6492
 
-Source: `https://docs.base.org/base-account/guides/authenticate-users`
+Source: `https://docs.base.org/base-account/guides/authenticate-users.md`
 
 ```ts
 // Sign‑in with Ethereum using a 6492‑compatible signature
@@ -199,8 +199,8 @@ const signature = await provider.request({ method: 'personal_sign', params: [mes
 Example: USDC checkout with paymaster sponsorship
 
 Sources:
-- `https://docs.base.org/base-account/guides/accept-payments`
-- `https://docs.base.org/base-account/improve-ux/sponsor-gas/paymasters`
+- `https://docs.base.org/base-account/guides/accept-payments.md`
+- `https://docs.base.org/base-account/improve-ux/sponsor-gas/paymasters.md`
 
 ```ts
 await provider.request({
@@ -217,7 +217,7 @@ await provider.request({
 
 Example: Create and use a sub‑account for scoped spend
 
-Source: `https://docs.base.org/base-account/improve-ux/sub-accounts`
+Source: `https://docs.base.org/base-account/improve-ux/sub-accounts.md`
 
 ```ts
 const sub = await account.createSubAccount({ label: 'checkout' })

docs/base-app/llms-full.txt

@@ -43,7 +43,7 @@ for await (const msg of await client.conversations.streamAllMessages()) {
 
 ## Quickstart (excerpts)
 
-Source: `https://docs.base.org/base-app/agents/getting-started`
+Source: `https://docs.base.org/base-app/agents/getting-started.md`
 
 Create an XMTP agent that can receive messages and reply, then evolve it to surface transaction trays for safe onchain actions.
 
@@ -65,28 +65,28 @@ for await (const msg of await client.conversations.streamAllMessages()) {
 }
 ```
 
-Source: `https://docs.base.org/base-app/agents/transaction-trays`
+Source: `https://docs.base.org/base-app/agents/transaction-trays.md`
 
 Transaction trays let you surface predefined, safe actions. Users approve in‑app; your agent never holds keys.
 
 
 ## Key Concepts (excerpts)
 
-Source: `https://docs.base.org/base-app/agents/why-agents`
+Source: `https://docs.base.org/base-app/agents/why-agents.md`
 
 - Safety: Agents propose actions; users approve in Base App with a smart wallet. No private keys leave the client.
 - UX: Transaction trays standardize onchain actions, reduce phishing, and help users understand intent.
 - Content types: Structured messages ensure predictable parsing and rendering across clients.
-  - Source: `https://docs.base.org/base-app/agents/content-types`
+  - Source: `https://docs.base.org/base-app/agents/content-types.md`
 - Distribution: Follow the featuring checklist to maximize discovery.
-  - Source: `https://docs.base.org/base-app/agents/getting-featured`
+  - Source: `https://docs.base.org/base-app/agents/getting-featured.md`
 
 
 ## API and Schemas (pruned)
 
 Message content types (subset):
 - Text, Button, Form, Transaction Tray
-  - Source: `https://docs.base.org/base-app/agents/content-types`
+  - Source: `https://docs.base.org/base-app/agents/content-types.md`
 
 Transaction tray schema (conceptual):
 
@@ -105,7 +105,7 @@ Transaction tray schema (conceptual):
 
 Example: Simple echo agent with guardrails
 
-Source: `https://docs.base.org/base-app/agents/best-practices`
+Source: `https://docs.base.org/base-app/agents/best-practices.md`
 
 ```ts
 if (!isSupportedContentType(msg)) return
@@ -116,7 +116,7 @@ await convo.send(text)
 
 Example: Surface a checkout action as a transaction tray
 
-Source: `https://docs.base.org/base-app/agents/transaction-trays`
+Source: `https://docs.base.org/base-app/agents/transaction-trays.md`
 
 ```ts
 await convo.send({

docs/base-chain/llms-full.txt

@@ -62,7 +62,7 @@
 
 ## Quickstart (excerpts)
 
-Source: `https://docs.base.org/base-chain/quickstart/deploy-on-base`
+Source: `https://docs.base.org/base-chain/quickstart/deploy-on-base.md`
 
 Deploy with Foundry to Base Sepolia:
 
@@ -73,7 +73,7 @@ forge create src/Contract.sol:Contract \
   --verify --verifier blockscout --verifier-url https://base-sepolia.blockscout.com/api
 ```
 
-Source: `https://docs.base.org/base-chain/quickstart/connecting-to-base`
+Source: `https://docs.base.org/base-chain/quickstart/connecting-to-base.md`
 
 Connect a client to Base:
 
@@ -87,36 +87,36 @@ const client = createPublicClient({ chain: base, transport: http() })
 
 ## Key Concepts (excerpts)
 
-Source: `https://docs.base.org/base-chain/network-information/diffs-ethereum-base`
+Source: `https://docs.base.org/base-chain/network-information/diffs-ethereum-base.md`
 
 - OP Stack rollup: Base batches L2 transactions and posts data to Ethereum L1, inheriting L1 security.
 - Fees: Total includes L2 execution and L1 data costs. See fee breakdown and estimator.
-  - Source: `https://docs.base.org/base-chain/network-information/network-fees`
+  - Source: `https://docs.base.org/base-chain/network-information/network-fees.md`
 - Canonical contracts: Use published address lists for bridges, system contracts, and registry.
-  - Source: `https://docs.base.org/base-chain/network-information/base-contracts`
+  - Source: `https://docs.base.org/base-chain/network-information/base-contracts.md`
 - Bridges: Official and third‑party bridge options for moving assets to/from Base.
-  - Source: `https://docs.base.org/base-chain/network-information/bridges-mainnet`
+  - Source: `https://docs.base.org/base-chain/network-information/bridges-mainnet.md`
 
 
 ## APIs and Tooling (pruned)
 
 - Onchain Registry API — discover verified projects and data on Base
-  - Source: `https://docs.base.org/base-chain/tools/onchain-registry-api`
+  - Source: `https://docs.base.org/base-chain/tools/onchain-registry-api.md`
 - Node Providers — RPC endpoints for Base and Base Sepolia
-  - Source: `https://docs.base.org/base-chain/tools/node-providers`
+  - Source: `https://docs.base.org/base-chain/tools/node-providers.md`
 - Block Explorers — Basescan and Blockscout URLs
-  - Source: `https://docs.base.org/base-chain/tools/block-explorers`
+  - Source: `https://docs.base.org/base-chain/tools/block-explorers.md`
 - Faucets — Get test ETH for Base Sepolia
-  - Source: `https://docs.base.org/base-chain/tools/network-faucets`
+  - Source: `https://docs.base.org/base-chain/tools/network-faucets.md`
 
 
 ## Node Operations (excerpts)
 
 Sources:
-- `https://docs.base.org/base-chain/node-operators/run-a-base-node`
-- `https://docs.base.org/base-chain/node-operators/performance-tuning`
-- `https://docs.base.org/base-chain/node-operators/snapshots`
-- `https://docs.base.org/base-chain/node-operators/troubleshooting`
+- `https://docs.base.org/base-chain/node-operators/run-a-base-node.md`
+- `https://docs.base.org/base-chain/node-operators/performance-tuning.md`
+- `https://docs.base.org/base-chain/node-operators/snapshots.md`
+- `https://docs.base.org/base-chain/node-operators/troubleshooting.md`
 
 - Architecture: Operate a rollup (consensus) node paired with an execution client. Ensure both services are healthy and in sync.
 - Provisioning: Use SSD storage, reliable network, and adhere to the current requirements listed in the run‑a‑node guide. Prefer containerized or systemd‑managed services for resilience.
@@ -138,9 +138,9 @@ curl -s -X POST "$BASE_RPC" -H 'content-type: application/json' \
 ## Flashblocks (excerpts)
 
 Sources:
-- `https://docs.base.org/base-chain/flashblocks/docs`
-- `https://docs.base.org/base-chain/flashblocks/apps`
-- `https://docs.base.org/base-chain/flashblocks/node-providers`
+- `https://docs.base.org/base-chain/flashblocks/docs.md`
+- `https://docs.base.org/base-chain/flashblocks/apps.md`
+- `https://docs.base.org/base-chain/flashblocks/node-providers.md`
 
 - Overview: Flashblocks resources aggregate information for builders and infra partners who need reliable, low‑latency access patterns on Base.
 - Ecosystem: Review apps that make use of Flashblocks‑related infra and the node providers who support relevant capabilities.
@@ -161,7 +161,7 @@ console.log('latencyMs', Date.now() - t0, 'number', block.number)
 
 Example: Bridge a token to Base (conceptual)
 
-Source: `https://docs.base.org/base-chain/quickstart/bridge-token`
+Source: `https://docs.base.org/base-chain/quickstart/bridge-token.md`
 
 ```text
 1) Visit the official bridge UI
@@ -172,7 +172,7 @@ Source: `https://docs.base.org/base-chain/quickstart/bridge-token`
 
 Example: Read a contract on Base with Viem
 
-Source: `https://docs.base.org/base-chain/quickstart/connecting-to-base`
+Source: `https://docs.base.org/base-chain/quickstart/connecting-to-base.md`
 
 ```ts
 import { createPublicClient, http } from 'viem'

docs/llms-full.txt

@@ -12,31 +12,31 @@
 
 ### Networks and environments
 Sources:
-- `https://docs.base.org/base-chain/quickstart/connecting-to-base`
-- `https://docs.base.org/base-chain/network-information/diffs-ethereum-base`
-- `https://docs.base.org/base-chain/tools/node-providers`
+- `https://docs.base.org/base-chain/quickstart/connecting-to-base.md`
+- `https://docs.base.org/base-chain/network-information/diffs-ethereum-base.md`
+- `https://docs.base.org/base-chain/tools/node-providers.md`
 
 > Base runs on Ethereum L2 with mainnet and Base Sepolia testnet. Use official RPCs from trusted node providers. Typical chain IDs: Base mainnet (8453), Base Sepolia (84532). Prefer HTTPS RPCs behind TLS, pin to provider domains, and handle occasional reorgs. For clients (e.g., Viem), configure the chain and transport explicitly; avoid relying on window-injected providers in server contexts.
 
 ### Authentication and API usage
 Sources:
-- `https://docs.base.org/base-account/guides/authenticate-users`
-- `https://docs.base.org/mini-apps/features/Authentication`
-- `https://docs.base.org/onchainkit/config/onchainkit-provider`
+- `https://docs.base.org/base-account/guides/authenticate-users.md`
+- `https://docs.base.org/mini-apps/features/Authentication.md`
+- `https://docs.base.org/onchainkit/config/onchainkit-provider.md`
 
 > Auth patterns vary by product. Use SIWE (ERC‑6492 compatible) for user sign-in where smart wallets may not yet exist. In Mini Apps, defer auth until needed; prefer scoped, revocable permissions and transaction trays for intent. For SDK/server APIs (e.g., OnchainKit), supply API keys via environment variables, rotate regularly, and verify server-side signatures or webhooks. Never store user passkeys or raw private keys server-side.
 
 ### Errors and retries
 Sources:
-- `https://docs.base.org/onchainkit/api/get-swap-quote`
-- `https://docs.base.org/base-chain/node-operators/troubleshooting`
+- `https://docs.base.org/onchainkit/api/get-swap-quote.md`
+- `https://docs.base.org/base-chain/node-operators/troubleshooting.md`
 
 > Expect standard JSON error envelopes with `code`, `message`, and optional `details`. Treat 429 as rate-limited: respect `Retry-After` and apply exponential backoff with jitter. For idempotent operations (payments, tx-build), include an idempotency key if supported. Distinguish user-declined actions from transport or server errors and surface clear recovery guidance to users.
 
 ### Rate limits
 Sources:
-- `https://docs.base.org/onchainkit/api/get-tokens`
-- `https://docs.base.org/base-chain/tools/node-providers`
+- `https://docs.base.org/onchainkit/api/get-tokens.md`
+- `https://docs.base.org/base-chain/tools/node-providers.md`
 
 > Rate limits vary by provider and endpoint. Batch reads when possible, cache static metadata, and use conditional requests. On 429, back off and retry after the indicated window. Avoid concurrent duplicate builds/quotes; fan out only when necessary.