Merge branch 'main' into framework/flask

Author: philsturgeon

_meta.global.tsx

@@ -23,7 +23,7 @@ Let's start with what each role player wants and think about how we can find com
 
 Compliance allows you to avoid paying hefty fines and losing customer trust.
 
-Take, for example, [the €290,000,000 GDPR fine Uber had to pay in July 2024](https://web.archive.org/web/20250712030312/https://www.edpb.europa.eu/news/news/2024/dutch-sa-imposes-fine-290-million-euro-uber-because-transfers-drivers-data-us_en) for improperly transferring European drivers' personal data to servers in the United States. Uber's API and data infrastructure failed to implement adequate safeguards when transmitting sensitive information, including location data, payment details, identification documents, and in some cases, even criminal and medical records.
+Take, for example, [the €290,000,000 GDPR fine Uber had to pay in July 2024](https://www.edpb.europa.eu/news/news/2024/dutch-sa-imposes-fine-290-million-euro-uber-because-transfers-drivers-data-us_en) for improperly transferring European drivers' personal data to servers in the United States. Uber's API and data infrastructure failed to implement adequate safeguards when transmitting sensitive information, including location data, payment details, identification documents, and in some cases, even criminal and medical records.
 
 This serves as a costly reminder that privacy compliance needs to be designed into APIs from the start, particularly for international data transfers. The cost of retrofitting compliance can far exceed the cost of building it in from the start.
 

api-design/api-compliance.mdx

@@ -164,7 +164,7 @@ more and more API teams.
 ```
 
 This example of an error from the [Signature
-API](https://signatureapi.com/docs/errors) includes a `type`, which is basically
+API](https://signatureapi.com/docs/api/errors) includes a `type`, which is basically
 the same as an error code, but instead of an arbitrary string like
 `invalid-api-key` the standard suggests a URI which is unique to the API (or
 ecosystem): `https://signatureapi.com/docs/v1/errors/invalid-api-key`. This does

api-design/errors.mdx

@@ -214,7 +214,7 @@ Key differences in these policies include how consent is obtained and region-spe
 Compliance certifications are often required to prove your API's security and reliability if you plan to work with large businesses or regulated industries. These certifications validate your data protection practices and operational processes. Some of the most widely recognized frameworks for API security and data protection include:
 
 - [SOC 2](https://www.imperva.com/learn/data-security/soc-2-compliance/): Confirms that your API meets security, availability, and confidentiality standards.
-- [ISO 27001](https://www.iso.org/standard/27001): An international standard for managing information security.
+- [ISO 27001](https://en.wikipedia.org/wiki/ISO/IEC_27001): An international standard for managing information security.
 - [PCI-DSS](https://www.pcisecuritystandards.org/): Required if your API handles payment card transactions.
 - [FedRAMP](https://www.fedramp.gov/): Necessary for providing services to U.S. government agencies.
 

api-design/expose-api-publicly.mdx

@@ -17,7 +17,7 @@ In the crunch-time rush to sign up your first enterprise customer, you may be te
 
 Pricing changes over time. We're not talking only about inflation or the price of eggs (although inflation plays a role); we're referring to the inevitable and often rapid changes you should expect in market conditions.
 
-Anticipating rather than fighting these changes can bring sustained competitive advantage in the face of the wonderful surprises the market inevitably brings: Competitive pivots, rapid market entry, customer bargaining, pricing experiments, product expansion, and shifting cost structures will all demand iterative pricing changes. These principles are inspired by the five pillars of [PriceOps](https://priceops.org/) and long nights of patching home-grown billing systems.
+Anticipating rather than fighting these changes can bring sustained competitive advantage in the face of the wonderful surprises the market inevitably brings: Competitive pivots, rapid market entry, customer bargaining, pricing experiments, product expansion, and shifting cost structures will all demand iterative pricing changes. These principles are inspired by the five pillars of [PriceOps](https://www.priceops.net/) and long nights of patching home-grown billing systems.
 
 When API functionality and monetization are tightly intertwined, even modest changes to pricing models will require code refactoring, pulling engineers away from core product development, growing organizational friction, and making expensive rewrites the norm.
 
@@ -235,7 +235,7 @@ This code assumes you have a Kafka producer running and a topic named `metering-
 
 ### Step 3: Centralize your pricing definitions
 
-Pricing plans should typically live in structured databases or systems designed explicitly for fast read/write and easy evolution, like a versioned NoSQL data store, a relational PostgreSQL database, or a dedicated billing platform (such as [Chargebee](https://www.chargebee.com/recurring-billing-invoicing/metered-usage-billing/), [Stripe Billing](https://docs.stripe.com/billing/subscriptions/usage-based/pricing-models), [Metronome](https://docs.metronome.com/pricing-packaging/), or [Lago](https://www.getlago.com/products/plans)).
+Pricing plans should typically live in structured databases or systems designed explicitly for fast read/write and easy evolution, like a versioned NoSQL data store, a relational PostgreSQL database, or a dedicated billing platform (such as [Chargebee](https://www.chargebee.com/recurring-billing-invoicing/metered-usage-billing/), [Stripe Billing](https://docs.stripe.com/billing/subscriptions/usage-based/pricing-models), [Metronome](https://docs.metronome.com/pricing-packaging/), or [Lago](https://www.getlago.com/solutions/use-cases/hybrid-plans)).
 
 Defining your pricing plans in a structured format allows you to version them, experiment with new plans, and roll back changes if necessary. It also enables you to build tooling (like dashboards, reports, and customer-facing pricing pages) around your pricing plans.
 

api-design/monetization.mdx

@@ -6,12 +6,16 @@ alwaysShowInSidebar: true
 
 import { Button } from "@/components/ui/button";
 import { CardGrid } from "@/mdx/components";
-import { cards, intro } from "@/lib/data/docs/overview";
-import { TechCards } from "@/components/card/variants/docs/tech-cards"; 
+import { cards, intro, cliInstall } from "@/lib/data/docs/overview";
+import { TechCards } from "@/components/card/variants/docs/tech-cards";
 import { DocsHeaderIndex } from "@/components/nextra/docs/docs-header-index";
+import { CodeWithTabs } from "@/components/code-tabs";
 
 <div className="docs-index bsmnt-container-md flex flex-col mt-10 gap-14">
   <DocsHeaderIndex title={intro?.title} description={intro?.description} />
+  <section className="-mt-8">
+    <CodeWithTabs tabs={cliInstall.tabs} className="max-w-[540px]" />
+  </section>
   <section>
     <CardGrid cards={cards?.start} heading="Start building" columns={4} />
   </section>

docs/gram/examples/open-ai-apps-sdk.mdx

@@ -117,7 +117,7 @@ Using the [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/ge
 
 ## Prerequisites
 
-- A [Gram account](/product/gram) (free)
+- A [Gram account](https://app.getgram.ai) (free)
 - An OpenAI API key from the [OpenAI dashboard](https://platform.openai.com/account/api-keys)
 - [Node.js](https://nodejs.org/) and [Docker](https://www.docker.com/) for local development
 

docs/gram/mcp-installation-guides.md

@@ -20,7 +20,7 @@ In this guide, we'll:
 
 ## Setting up the project
 
-First, create a new Gram Functions project. Follow the instructions in the [Getting Started](/docs/gram/getting-started) guide for more details.
+First, create a new Gram Functions project. Follow the instructions in the [Getting Started](/docs/mcp/getting-started) guide for more details.
 
 ```bash
 npm create gram-functions@latest
@@ -298,12 +298,12 @@ const API_KEY = "abc123...";
 
 Now that you understand how to consume external APIs with Gram Functions, explore these related guides:
 
-- [Build MCP servers with external OAuth](/docs/gram/examples/oauth-external-server)
-- [Creating an MCP server for Taskmaster](/docs/gram/examples/creating-taskmaster-mcp-server)
-- [Deploy from GitHub Actions](/docs/gram/examples/deploy-from-github-actions)
+- [Build MCP servers with external OAuth](/docs/mcp/build/examples/oauth-external-server)
+- [Creating an MCP server for Taskmaster](/docs/mcp/build/examples/creating-taskmaster-mcp-server)
+- [Deploy from GitHub Actions](/docs/mcp/build/examples/deploy-from-github-actions)
 
 ## Additional resources
 
 - [OpenWeatherMap API Documentation](https://openweathermap.org/api)
-- [Gram Functions API Reference](/docs/gram/gram-functions/introduction)
+- [Gram Functions API Reference](/docs/mcp/build/gram-functions)
 - [Zod Schema Validation](https://zod.dev)