[{
"path": "/store/3scale/",
"title": "3Scale",
"subtitle": "The freemium-first API management platform that proved the space could be self-service and sustainable.",
"slug": "3scale",
"tags": ["History","API Management"]
},{
"path": "/store/access/",
"title": "Access",
"subtitle": "Who gets to call an API and under what terms",
"slug": "access",
"tags": ["Politics"]
},{
"path": "/store/accountability/",
"title": "Accountability",
"subtitle": "Mechanisms for holding API providers responsible for their platform decisions",
"slug": "accountability",
"tags": ["Politics"]
},{
"path": "/store/advocacy/",
"title": "Advocacy",
"subtitle": "Public or internal championing of APIs and the developers who build on them",
"slug": "advocacy",
"tags": ["Evangelism"]
},{
"path": "/store/agent-skills/",
"title": "Agent Skills",
"subtitle": "Packaged capability units that AI agents load to execute API operations",
"slug": "agent-skills",
"tags": ["Technology"]
},{
"path": "/store/aggregators/",
"title": "Aggregators",
"subtitle": "Services that unify multiple provider APIs behind a single interface",
"slug": "aggregators",
"tags": ["Business"]
},{
"path": "/store/amazon/",
"title": "Amazon",
"subtitle": "The e-commerce and cloud company that bet its entire platform on APIs",
"slug": "amazon",
"tags": ["History"]
},{
"path": "/store/antitrust/",
"title": "Antitrust",
"subtitle": "APIs as competitive weapons, and the platform power that regulation is finally confronting",
"slug": "antitrust",
"tags": ["Politics"]
},{
"path": "/store/apigee/",
"title": "Apigee",
"subtitle": "The API management leader that defined enterprise API gateway practices",
"slug": "apigee",
"tags": ["History"]
},{
"path": "/store/apis-json/",
"title": "APIs.json",
"subtitle": "The machine-readable discovery format I created for indexing APIs and their operations",
"slug": "apis-json",
"tags": ["Technology"]
},{
"path": "/store/arazzo/",
"title": "Arazzo",
"subtitle": "The OpenAPI Initiative specification for describing multi-step API workflows",
"slug": "arazzo",
"tags": ["Technology"]
},{
"path": "/store/artifacts/",
"title": "Artifacts",
"subtitle": "Machine-readable definitions that drive automation across the entire API lifecycle",
"slug": "artifacts",
"tags": ["Technology"]
},{
"path": "/store/async/",
"title": "Async",
"subtitle": "Governing asynchronous and event-driven API patterns alongside REST",
"slug": "async",
"tags": ["Governance"]
},{
"path": "/store/asyncapi/",
"title": "AsyncAPI",
"subtitle": "The specification standard for event-driven and messaging APIs",
"slug": "asyncapi",
"tags": ["Technology"]
},{
"path": "/store/audits/",
"title": "Audits",
"subtitle": "Systematic reviews of API access logs decisions and compliance posture",
"slug": "audits",
"tags": ["Politics"]
},{
"path": "/store/authentication/",
"title": "Authentication",
"subtitle": "Verifying the identity of API consumers before granting access",
"slug": "authentication",
"tags": ["Technology"]
},{
"path": "/store/awareness/",
"title": "Awareness",
"subtitle": "The understanding of your infrastructure, applications, and operations that working with APIs forces into the open",
"slug": "awareness",
"tags": ["Governance"]
},{
"path": "/store/aws/",
"title": "AWS",
"subtitle": "Amazon Web Services that turned infrastructure into programmable API primitives",
"slug": "aws",
"tags": ["History"]
},{
"path": "/store/blogs/",
"title": "Blogs",
"subtitle": "Owned editorial channels for publishing API stories tutorials and opinions",
"slug": "blogs",
"tags": ["Evangelism"]
},{
"path": "/store/capabilities/",
"title": "Capabilities",
"subtitle": "Business-aligned, self-describing units of what an organization can do, governed across business and engineering",
"slug": "capabilities",
"tags": ["Governance"]
},{
"path": "/store/capital-g-governance/",
"title": "Capital-G Governance",
"subtitle": "Formal top-down governance programs with mandated rules and enforcement",
"slug": "capital-g-governance",
"tags": ["Governance"]
},{
"path": "/store/changes/",
"title": "Changes",
"subtitle": "Managing and governing breaking and non-breaking API changes over time",
"slug": "changes",
"tags": ["Governance"]
},{
"path": "/store/ci-cd/",
"title": "CI/CD",
"subtitle": "Continuous integration and delivery pipelines for automating API lifecycle stages",
"slug": "ci-cd",
"tags": ["Technology"]
},{
"path": "/store/cli/",
"title": "CLI",
"subtitle": "Command-line tooling as an interface to APIs across producing, consuming, governance, and MCP",
"slug": "cli",
"tags": ["Governance"]
},{
"path": "/store/clients/",
"title": "Clients",
"subtitle": "Tools and libraries consumers use to call and interact with APIs",
"slug": "clients",
"tags": ["Technology"]
},{
"path": "/store/collections/",
"title": "Collections",
"subtitle": "Portable executable bundles of API requests as a fundamental API artifact",
"slug": "collections",
"tags": ["Technology"]
},{
"path": "/store/commons/",
"title": "Commons",
"subtitle": "APIs and data held as shared public goods rather than proprietary assets",
"slug": "commons",
"tags": ["Politics"]
},{
"path": "/store/communities/",
"title": "Communities",
"subtitle": "Developer communities built around an API platform or ecosystem",
"slug": "communities",
"tags": ["Business"]
},{
"path": "/store/compliance/",
"title": "Compliance",
"subtitle": "Meeting legal and regulatory requirements through API design and operations",
"slug": "compliance",
"tags": ["Politics"]
},{
"path": "/store/consent/",
"title": "Consent",
"subtitle": "The political question of whether people actually agree to how their data flows through APIs",
"slug": "consent",
"tags": ["Politics"]
},{
"path": "/store/consumption/",
"title": "Consumption",
"subtitle": "Governing how APIs are consumed and what patterns consumers should follow",
"slug": "consumption",
"tags": ["Governance"]
},{
"path": "/store/control/",
"title": "Control",
"subtitle": "The mechanisms by which API providers determine what consumers can do",
"slug": "control",
"tags": ["Politics"]
},{
"path": "/store/conversations/",
"title": "Conversations",
"subtitle": "One-on-one and small-group exchanges that deepen developer relationships",
"slug": "conversations",
"tags": ["Evangelism"]
},{
"path": "/store/copilots/",
"title": "Copilots",
"subtitle": "AI coding assistants integrated into the API development workflow",
"slug": "copilots",
"tags": ["Technology"]
},{
"path": "/store/copyright/",
"title": "Copyright",
"subtitle": "The decade-long fight over whether API interfaces can be owned",
"slug": "copyright",
"tags": ["Politics"]
},{
"path": "/store/corba/",
"title": "CORBA",
"subtitle": "Common Object Request Broker Architecture the heavyweight distributed computing predecessor",
"slug": "corba",
"tags": ["History"]
},{
"path": "/store/cost/",
"title": "Cost",
"subtitle": "The financial and operational cost of API sprawl inconsistency and rework",
"slug": "cost",
"tags": ["Governance"]
},{
"path": "/store/customers/",
"title": "Customers",
"subtitle": "The organizations and individuals who consume APIs as business value",
"slug": "customers",
"tags": ["Business"]
},{
"path": "/store/delicious/",
"title": "Delicious",
"subtitle": "The social bookmarking service that helped popularize REST and tagging via API",
"slug": "delicious",
"tags": ["History"]
},{
"path": "/store/democracy/",
"title": "Democracy",
"subtitle": "APIs as infrastructure for transparency, accountability, and public participation",
"slug": "democracy",
"tags": ["Politics"]
},{
"path": "/store/deployment/",
"title": "Deployment",
"subtitle": "The many shapes and sizes of how APIs are actually stood up and served",
"slug": "deployment",
"tags": ["Technology"]
},{
"path": "/store/deprecation/",
"title": "Deprecation",
"subtitle": "The managed process of retiring an API version or endpoint",
"slug": "deprecation",
"tags": ["Business"]
},{
"path": "/store/design/",
"title": "Design",
"subtitle": "The discipline of designing APIs deliberately before and as they are built",
"slug": "design",
"tags": ["Technology"]
},{
"path": "/store/developers/",
"title": "Developers",
"subtitle": "The primary audience building integrations and applications on APIs",
"slug": "developers",
"tags": ["Evangelism"]
},{
"path": "/store/devrel/",
"title": "DevRel",
"subtitle": "Developer relations programs that support the full developer experience",
"slug": "devrel",
"tags": ["Evangelism"]
},{
"path": "/store/discovery/",
"title": "Discovery",
"subtitle": "Finding and cataloging APIs across an organization or the web",
"slug": "discovery",
"tags": ["Technology"]
},{
"path": "/store/documentation/",
"title": "Documentation",
"subtitle": "Human-readable reference material generated from API definitions",
"slug": "documentation",
"tags": ["Technology"]
},{
"path": "/store/ebay/",
"title": "eBay",
"subtitle": "An early adopter of the marketplace API model enabling third-party commerce",
"slug": "ebay",
"tags": ["History"]
},{
"path": "/store/economy/",
"title": "Economy",
"subtitle": "The market of value created and exchanged through APIs",
"slug": "economy",
"tags": ["Business"]
},{
"path": "/store/edi/",
"title": "EDI",
"subtitle": "Electronic Data Interchange the original machine-to-machine business integration",
"slug": "edi",
"tags": ["History"]
},{
"path": "/store/editors/",
"title": "Editors",
"subtitle": "Text and visual editors with inline governance feedback",
"slug": "editors",
"tags": ["Governance"]
},{
"path": "/store/education/",
"title": "Education",
"subtitle": "Teaching API literacy and the politics of who learns and who is excluded",
"slug": "education",
"tags": ["Politics"]
},{
"path": "/store/elections/",
"title": "Elections",
"subtitle": "APIs in civic infrastructure voter data and the politics of electoral systems",
"slug": "elections",
"tags": ["Politics"]
},{
"path": "/store/engines/",
"title": "Engines",
"subtitle": "The runtime tooling that evaluates rules against API definitions",
"slug": "engines",
"tags": ["Governance"]
},{
"path": "/store/epistemological/",
"title": "Epistemological",
"subtitle": "Governance grounded in how we know and validate what is true about APIs",
"slug": "epistemological",
"tags": ["Governance"]
},{
"path": "/store/evangelism/",
"title": "Evangelism",
"subtitle": "The practice of carrying the API message and earning adoption through belief",
"slug": "evangelism",
"tags": ["Evangelism"]
},{
"path": "/store/event-destinations/",
"title": "Event Destinations",
"subtitle": "Configurable targets for routing API events to downstream systems",
"slug": "event-destinations",
"tags": ["Technology"]
},{
"path": "/store/event-driven/",
"title": "Event-Driven",
"subtitle": "Architecture where APIs communicate through asynchronous event streams",
"slug": "event-driven",
"tags": ["Technology"]
},{
"path": "/store/experience/",
"title": "Experience",
"subtitle": "The end-to-end quality of the journey developers have with an API program",
"slug": "experience",
"tags": ["Evangelism"]
},{
"path": "/store/external/",
"title": "External",
"subtitle": "Outreach and storytelling aimed at the public developer community",
"slug": "external",
"tags": ["Evangelism"]
},{
"path": "/store/facebook/",
"title": "Facebook",
"subtitle": "The social platform that pioneered the platform API strategy and its consequences",
"slug": "facebook",
"tags": ["History"]
},{
"path": "/store/feedback-loops/",
"title": "Feedback Loops",
"subtitle": "Structured channels for developers to report problems and influence the roadmap",
"slug": "feedback-loops",
"tags": ["Evangelism"]
},{
"path": "/store/flickr/",
"title": "Flickr",
"subtitle": "The social photo platform whose API defined the mashup era",
"slug": "flickr",
"tags": ["History"]
},{
"path": "/store/foursquare/",
"title": "Foursquare",
"subtitle": "The location API company at the center of the mobile-social API era",
"slug": "foursquare",
"tags": ["History"]
},{
"path": "/store/gateways/",
"title": "Gateways",
"subtitle": "Proxies that manage routing authentication rate-limiting and observability for APIs",
"slug": "gateways",
"tags": ["Technology"]
},{
"path": "/store/git/",
"title": "Git",
"subtitle": "Version control as the source of truth for API definitions and code",
"slug": "git",
"tags": ["Technology"]
},{
"path": "/store/google/",
"title": "Google",
"subtitle": "The company whose API sprawl shaped both developer expectations and governance challenges",
"slug": "google",
"tags": ["History"]
},{
"path": "/store/government/",
"title": "Government",
"subtitle": "Public sector APIs from open data initiatives to regulated interoperability mandates",
"slug": "government",
"tags": ["History"]
},{
"path": "/store/graphql/",
"title": "GraphQL",
"subtitle": "A query language and runtime for flexible API data fetching",
"slug": "graphql",
"tags": ["Technology"]
},{
"path": "/store/grpc/",
"title": "gRPC",
"subtitle": "Google Remote Procedure Call as an alternative high-performance API protocol",
"slug": "grpc",
"tags": ["Governance"]
},{
"path": "/store/guardrails/",
"title": "Guardrails",
"subtitle": "Rules and checks that prevent harmful patterns without blocking progress",
"slug": "guardrails",
"tags": ["Governance"]
},{
"path": "/store/hackathons/",
"title": "Hackathons",
"subtitle": "The evangelism event that energizes a community but rarely delivers the outcomes its sponsors expect",
"slug": "hackathons",
"tags": ["Evangelism"]
},{
"path": "/store/http-1-1/",
"title": "HTTP 1.1",
"subtitle": "The foundational version of HTTP that powers REST APIs",
"slug": "http-1-1",
"tags": ["Technology"]
},{
"path": "/store/http-2/",
"title": "HTTP/2",
"subtitle": "Multiplexed connections and server push for faster API communication",
"slug": "http-2",
"tags": ["Technology"]
},{
"path": "/store/http-3/",
"title": "HTTP/3",
"subtitle": "QUIC-based HTTP for low-latency API delivery",
"slug": "http-3",
"tags": ["Technology"]
},{
"path": "/store/hypermedia/",
"title": "Hypermedia",
"subtitle": "API design that embeds navigational links in responses",
"slug": "hypermedia",
"tags": ["Technology"]
},{
"path": "/store/ide/",
"title": "IDE",
"subtitle": "Integrated development environments with API tooling and governance inline",
"slug": "ide",
"tags": ["Technology"]
},{
"path": "/store/industries/",
"title": "Industries",
"subtitle": "Sector-specific API politics from banking and healthcare to energy and media",
"slug": "industries",
"tags": ["Politics"]
},{
"path": "/store/instagram/",
"title": "Instagram",
"subtitle": "The photo-sharing platform that rose and closed its API in a cautionary arc",
"slug": "instagram",
"tags": ["History"]
},{
"path": "/store/integration/",
"title": "Integration",
"subtitle": "Connecting systems through APIs as the work that actually matters to business",
"slug": "integration",
"tags": ["Technology"]
},{
"path": "/store/internal/",
"title": "Internal",
"subtitle": "Evangelism directed at teams and stakeholders inside the organization",
"slug": "internal",
"tags": ["Evangelism"]
},{
"path": "/store/interoperability/",
"title": "Interoperability",
"subtitle": "Mandated or voluntary ability for different systems to exchange data via API",
"slug": "interoperability",
"tags": ["Politics"]
},{
"path": "/store/journalism/",
"title": "Journalism",
"subtitle": "Press access to APIs and the role of APIs in newsgathering and publishing",
"slug": "journalism",
"tags": ["Politics"]
},{
"path": "/store/json-api/",
"title": "JSON API",
"subtitle": "A specification for building APIs in JSON with resource relationships",
"slug": "json-api",
"tags": ["Technology"]
},{
"path": "/store/json-ld/",
"title": "JSON-LD",
"subtitle": "Linked data format that brings semantic meaning to API payloads",
"slug": "json-ld",
"tags": ["Technology"]
},{
"path": "/store/json-schema/",
"title": "JSON Schema",
"subtitle": "Vocabulary for annotating and validating JSON data structures",
"slug": "json-schema",
"tags": ["Technology"]
},{
"path": "/store/jwt/",
"title": "JWT",
"subtitle": "Compact signed tokens for conveying API identity and claims",
"slug": "jwt",
"tags": ["Technology"]
},{
"path": "/store/keys/",
"title": "Keys",
"subtitle": "API keys as the simplest token-based mechanism for authenticating requests",
"slug": "keys",
"tags": ["Technology"]
},{
"path": "/store/labor/",
"title": "Labor",
"subtitle": "The human work behind APIs and the power dynamics in who builds them",
"slug": "labor",
"tags": ["Politics"]
},{
"path": "/store/landscape/",
"title": "Landscape",
"subtitle": "The full map of APIs teams and operations that governance must cover",
"slug": "landscape",
"tags": ["Governance"]
},{
"path": "/store/lifecycle/",
"title": "Lifecycle",
"subtitle": "The end-to-end stages through which an API is designed built and retired",
"slug": "lifecycle",
"tags": ["Governance"]
},{
"path": "/store/literacy/",
"title": "Literacy",
"subtitle": "The baseline HTTP and API design knowledge governance programs depend on",
"slug": "literacy",
"tags": ["Governance"]
},{
"path": "/store/lowercase-g-governance/",
"title": "Lowercase-g Governance",
"subtitle": "Lightweight practical guidance that teams actually follow",
"slug": "lowercase-g-governance",
"tags": ["Governance"]
},{
"path": "/store/management/",
"title": "Management",
"subtitle": "The operational layer controlling API access analytics policies and plans",
"slug": "management",
"tags": ["Business"]
},{
"path": "/store/marketing/",
"title": "Marketing",
"subtitle": "Campaigns and content that generate awareness of an API program",
"slug": "marketing",
"tags": ["Evangelism"]
},{
"path": "/store/marketplaces/",
"title": "Marketplaces",
"subtitle": "Platforms where API providers list and consumers discover and purchase APIs",
"slug": "marketplaces",
"tags": ["Business"]
},{
"path": "/store/mashery/",
"title": "Mashery",
"subtitle": "One of the first API management platforms shaping the commercial API layer",
"slug": "mashery",
"tags": ["History"]
},{
"path": "/store/mcp/",
"title": "MCP",
"subtitle": "Model Context Protocol enabling AI agents to call tools and APIs",
"slug": "mcp",
"tags": ["Technology"]
},{
"path": "/store/meetups/",
"title": "Meetups",
"subtitle": "In-person and virtual gatherings of the API developer community",
"slug": "meetups",
"tags": ["Evangelism"]
},{
"path": "/store/microservices/",
"title": "Microservices",
"subtitle": "Architectural pattern of small independently deployable API services",
"slug": "microservices",
"tags": ["Technology"]
},{
"path": "/store/mocking/",
"title": "Mocking",
"subtitle": "Simulating API responses before the backend is built",
"slug": "mocking",
"tags": ["Technology"]
},{
"path": "/store/monetization/",
"title": "Monetization",
"subtitle": "Turning API consumption into direct or indirect revenue",
"slug": "monetization",
"tags": ["Business"]
},{
"path": "/store/mulesoft/",
"title": "MuleSoft",
"subtitle": "The integration vendor whose acquisitions traced the consolidation of the API space",
"slug": "mulesoft",
"tags": ["History"]
},{
"path": "/store/netflix/",
"title": "Netflix",
"subtitle": "The most successful API failure ever, and the lesson it taught the whole industry",
"slug": "netflix",
"tags": ["History"]
},{
"path": "/store/newsletters/",
"title": "Newsletters",
"subtitle": "Regular email publications that sustain developer awareness and engagement",
"slug": "newsletters",
"tags": ["Evangelism"]
},{
"path": "/store/oauth/",
"title": "OAuth",
"subtitle": "The delegation framework for granting third-party API access",
"slug": "oauth",
"tags": ["Technology"]
},{
"path": "/store/observability/",
"title": "Observability",
"subtitle": "Logs metrics and traces that reveal API runtime behavior",
"slug": "observability",
"tags": ["Technology"]
},{
"path": "/store/onboarding/",
"title": "Onboarding",
"subtitle": "The developer experience of moving from signup to first successful API call",
"slug": "onboarding",
"tags": ["Evangelism"]
},{
"path": "/store/ontological/",
"title": "Ontological",
"subtitle": "Governance grounded in shared definitions of what things are",
"slug": "ontological",
"tags": ["Governance"]
},{
"path": "/store/open-data/",
"title": "Open Data",
"subtitle": "Government and institutional commitments to make data publicly accessible via API",
"slug": "open-data",
"tags": ["Politics"]
},{
"path": "/store/open-source/",
"title": "Open-Source",
"subtitle": "APIs and tooling released under open licenses driving ecosystem adoption",
"slug": "open-source",
"tags": ["Business"]
},{
"path": "/store/openapi/",
"title": "OpenAPI",
"subtitle": "The machine-readable contract standard for HTTP APIs",
"slug": "openapi",
"tags": ["Technology"]
},{
"path": "/store/overlays/",
"title": "Overlays",
"subtitle": "The OpenAPI specification for applying targeted modifications without altering the base",
"slug": "overlays",
"tags": ["Technology"]
},{
"path": "/store/ownership/",
"title": "Ownership",
"subtitle": "The political struggle over who actually owns your data and your digital life",
"slug": "ownership",
"tags": ["Politics"]
},{
"path": "/store/partners/",
"title": "Partners",
"subtitle": "Organizations granted elevated API access to build joint business value",
"slug": "partners",
"tags": ["Business"]
},{
"path": "/store/partnerships/",
"title": "Partnerships",
"subtitle": "Co-marketing and co-evangelism with aligned platform and integration partners",
"slug": "partnerships",
"tags": ["Evangelism"]
},{
"path": "/store/people/",
"title": "People",
"subtitle": "The humans whose behavior and collaboration API governance is really about",
"slug": "people",
"tags": ["Governance"]
},{
"path": "/store/plans/",
"title": "Plans",
"subtitle": "Bundles of API access limits and features offered to consumers",
"slug": "plans",
"tags": ["Business"]
},{
"path": "/store/platform/",
"title": "Platform",
"subtitle": "APIs as the foundation of platform businesses and their political economy",
"slug": "platform",
"tags": ["Politics"]
},{
"path": "/store/platforms/",
"title": "Platforms",
"subtitle": "The underlying infrastructure and tooling on which API programs are built",
"slug": "platforms",
"tags": ["Business"]
},{
"path": "/store/podcasts/",
"title": "Podcasts",
"subtitle": "Long-form audio conversations that build trust and authority in the API space",
"slug": "podcasts",
"tags": ["Evangelism"]
},{
"path": "/store/policies/",
"title": "Policies",
"subtitle": "The human and business rationale behind every governance rule",
"slug": "policies",
"tags": ["Governance"]
},{
"path": "/store/postman/",
"title": "Postman",
"subtitle": "The API client that became the collaboration platform for the entire lifecycle",
"slug": "postman",
"tags": ["History"]
},{
"path": "/store/power/",
"title": "Power",
"subtitle": "The asymmetric relationships between platforms developers and end users mediated by APIs",
"slug": "power",
"tags": ["Politics"]
},{
"path": "/store/pricing/",
"title": "Pricing",
"subtitle": "The structure for monetizing API consumption by volume tier or feature",
"slug": "pricing",
"tags": ["Business"]
},{
"path": "/store/privacy/",
"title": "Privacy",
"subtitle": "The political struggle over personal data and who controls it through APIs",
"slug": "privacy",
"tags": ["Politics"]
},{
"path": "/store/production/",
"title": "Production",
"subtitle": "Governing APIs that are live and serving real traffic",
"slug": "production",
"tags": ["Governance"]
},{
"path": "/store/products/",
"title": "Products",
"subtitle": "Treating APIs as products with roadmaps owners and lifecycle management",
"slug": "products",
"tags": ["Business"]
},{
"path": "/store/programmableweb/",
"title": "ProgrammableWeb",
"subtitle": "The original API directory that documented and defined the early API economy",
"slug": "programmableweb",
"tags": ["History"]
},{
"path": "/store/provenance/",
"title": "Provenance",
"subtitle": "The history and origin story behind why a rule or pattern exists",
"slug": "provenance",
"tags": ["Governance"]
},{
"path": "/store/quality/",
"title": "Quality",
"subtitle": "The measurable correctness consistency and completeness of API definitions",
"slug": "quality",
"tags": ["Governance"]
},{
"path": "/store/rate-limiting/",
"title": "Rate Limiting",
"subtitle": "The technical mechanism for controlling how much consumers can use an API",
"slug": "rate-limiting",
"tags": ["Technology"]
},{
"path": "/store/regions/",
"title": "Regions",
"subtitle": "Geographic and jurisdictional considerations in API deployment and data residency",
"slug": "regions",
"tags": ["Politics"]
},{
"path": "/store/regulation/",
"title": "Regulation",
"subtitle": "Government and agency rules that mandate how APIs must behave",
"slug": "regulation",
"tags": ["Politics"]
},{
"path": "/store/regulations/",
"title": "Regulations",
"subtitle": "Legal and compliance requirements governing API data access and operations",
"slug": "regulations",
"tags": ["Business"]
},{
"path": "/store/releases/",
"title": "Releases",
"subtitle": "Versioned milestones marking new API capabilities delivered to consumers",
"slug": "releases",
"tags": ["Business"]
},{
"path": "/store/research/",
"title": "Research",
"subtitle": "Academic and scientific use of APIs for data collection and study",
"slug": "research",
"tags": ["Politics"]
},{
"path": "/store/rest/",
"title": "REST",
"subtitle": "Representational state transfer as the dominant HTTP API architectural style",
"slug": "rest",
"tags": ["Governance"]
},{
"path": "/store/road-maps/",
"title": "Road Maps",
"subtitle": "Public or internal plans communicating future API capabilities and timelines",
"slug": "road-maps",
"tags": ["Business"]
},{
"path": "/store/rpc/",
"title": "RPC",
"subtitle": "Remote Procedure Call the precursor model to modern web APIs",
"slug": "rpc",
"tags": ["History"]
},{
"path": "/store/rules/",
"title": "Rules",
"subtitle": "Machine-executable checks applied to API definitions at any lifecycle stage",
"slug": "rules",
"tags": ["Governance"]
},{
"path": "/store/sales/",
"title": "Sales",
"subtitle": "Assisted sales motions layered on top of an API self-service funnel",
"slug": "sales",
"tags": ["Evangelism"]
},{
"path": "/store/salesforce/",
"title": "Salesforce",
"subtitle": "The first major enterprise SaaS company to open its platform via API in 2000",
"slug": "salesforce",
"tags": ["History"]
},{
"path": "/store/sdks/",
"title": "SDKs",
"subtitle": "Generated language-native libraries that wrap API operations",
"slug": "sdks",
"tags": ["Technology"]
},{
"path": "/store/security/",
"title": "Security",
"subtitle": "Protecting APIs from unauthorized access abuse and vulnerabilities",
"slug": "security",
"tags": ["Technology"]
},{
"path": "/store/self-service/",
"title": "Self-Service",
"subtitle": "On-demand API access without sales or manual onboarding friction",
"slug": "self-service",
"tags": ["Business"]
},{
"path": "/store/semantic-versioning/",
"title": "Semantic Versioning",
"subtitle": "A versioning convention communicating the scope of API changes",
"slug": "semantic-versioning",
"tags": ["Technology"]
},{
"path": "/store/serverless/",
"title": "Serverless",
"subtitle": "Function-as-a-service compute that powers on-demand API execution",
"slug": "serverless",
"tags": ["Technology"]
},{
"path": "/store/slas/",
"title": "SLAs",
"subtitle": "Service level agreements as the commitments that make APIs dependable",
"slug": "slas",
"tags": ["Business"]
},{
"path": "/store/soap/",
"title": "SOAP",
"subtitle": "The older generation of web services that the web API economy grew up rejecting",
"slug": "soap",
"tags": ["History"]
},{
"path": "/store/social-media/",
"title": "Social Media",
"subtitle": "Platforms for real-time API storytelling and community engagement",
"slug": "social-media",
"tags": ["Evangelism"]
},{
"path": "/store/sovereignty/",
"title": "Sovereignty",
"subtitle": "National or regional control over data flows and API infrastructure",
"slug": "sovereignty",
"tags": ["Politics"]
},{
"path": "/store/spectral-rules/",
"title": "Spectral Rules",
"subtitle": "Linting rules for enforcing API design standards via Spectral",
"slug": "spectral-rules",
"tags": ["Technology"]
},{
"path": "/store/standards/",
"title": "Standards",
"subtitle": "Industry or regulatory agreements shaping how APIs are built and interoperate",
"slug": "standards",
"tags": ["Business"]
},{
"path": "/store/status/",
"title": "Status",
"subtitle": "Public communication about API availability incidents and degradation",
"slug": "status",
"tags": ["Politics"]
},{
"path": "/store/storytelling/",
"title": "Storytelling",
"subtitle": "Narrative as the most important tool in the API evangelism toolbox",
"slug": "storytelling",
"tags": ["Evangelism"]
},{
"path": "/store/strategy/",
"title": "Strategy",
"subtitle": "The deliberate, business-aligned plan that guides an organization's API efforts",
"slug": "strategy",
"tags": ["Business"]
},{
"path": "/store/stripe/",
"title": "Stripe",
"subtitle": "The payments company that set the modern bar for API developer experience",
"slug": "stripe",
"tags": ["History"]
},{
"path": "/store/style-guide/",
"title": "Style Guide",
"subtitle": "Documented API design conventions that inform and generate governance rules",
"slug": "style-guide",
"tags": ["Governance"]
},{
"path": "/store/support/",
"title": "Support",
"subtitle": "The ongoing human commitment that keeps API consumers unblocked and trusting",
"slug": "support",
"tags": ["Business"]
},{
"path": "/store/surveillance/",
"title": "Surveillance",
"subtitle": "APIs used to collect monitor or analyze human behavior at scale",
"slug": "surveillance",
"tags": ["Politics"]
},{
"path": "/store/swagger/",
"title": "Swagger",
"subtitle": "The API definition format that became OpenAPI and gave the industry a common language",
"slug": "swagger",
"tags": ["History"]
},{
"path": "/store/talent-acquisition/",
"title": "Talent Acquisition",
"subtitle": "Using the developer community as a pipeline for engineering and product hires",
"slug": "talent-acquisition",
"tags": ["Evangelism"]
},{
"path": "/store/testing/",
"title": "Testing",
"subtitle": "Verifying API behavior against the contract and expected outcomes",
"slug": "testing",
"tags": ["Technology"]
},{
"path": "/store/traceability/",
"title": "Traceability",
"subtitle": "Distributed tracing that follows a request across API service boundaries",
"slug": "traceability",
"tags": ["Technology"]
},{
"path": "/store/transparency/",
"title": "Transparency",
"subtitle": "Public disclosure of how APIs work who can access them and what they cost",
"slug": "transparency",
"tags": ["Politics"]
},{
"path": "/store/trust/",
"title": "Trust",
"subtitle": "The earned confidence that an API will behave as documented and promised",
"slug": "trust",
"tags": ["Politics"]
},{
"path": "/store/twilio/",
"title": "Twilio",
"subtitle": "The cloud communications company that proved the API-as-product business model",
"slug": "twilio",
"tags": ["History"]
},{
"path": "/store/twitter/",
"title": "Twitter",
"subtitle": "The platform whose API both enabled and then constrained an entire ecosystem",
"slug": "twitter",
"tags": ["History"]
},{
"path": "/store/vacuum-rules/",
"title": "Vacuum Rules",
"subtitle": "High-performance OpenAPI linting rules via the Vacuum engine",
"slug": "vacuum-rules",
"tags": ["Technology"]
},{
"path": "/store/value/",
"title": "Value",
"subtitle": "The truth that an API has no value until it is actually used",
"slug": "value",
"tags": ["Business"]
},{
"path": "/store/velocity/",
"title": "Velocity",
"subtitle": "The speed at which teams can ship APIs without accumulating quality debt",
"slug": "velocity",
"tags": ["Governance"]
},{
"path": "/store/vendors/",
"title": "Vendors",
"subtitle": "The API service providers an organization depends on and the strategy for choosing them",
"slug": "vendors",
"tags": ["Business"]
},{
"path": "/store/video/",
"title": "Video",
"subtitle": "The evangelism channel that shows developers how rather than just telling them",
"slug": "video",
"tags": ["Evangelism"]
},{
"path": "/store/webhooks/",
"title": "Webhooks",
"subtitle": "HTTP callbacks that push events from producer to consumer",
"slug": "webhooks",
"tags": ["Technology"]
},{
"path": "/store/workshops/",
"title": "Workshops",
"subtitle": "Hands-on teaching sessions where developers learn API skills directly",
"slug": "workshops",
"tags": ["Evangelism"]
},{
"path": "/store/zapier/",
"title": "Zapier",
"subtitle": "The platform that democratized API integration and built the citizen-integrator economy",
"slug": "zapier",
"tags": ["History"]
}]