diff --git a/apps/web/src/app/page.tsx b/apps/web/src/app/page.tsx
index c1c95ee1..ab345098 100644
--- a/apps/web/src/app/page.tsx
+++ b/apps/web/src/app/page.tsx
@@ -1,41 +1,16 @@
import Link from 'next/link'
-import { highlight } from '@/components/code-block/highlight'
import { DemandSideCTA } from '@/components/demand-side-cta'
import { DotsSection } from '@/components/dots-section'
-import { ExampleUsage } from '@/components/example-usage'
+import { ExampleUsageSection } from '@/components/example-usage-section'
import { GitHubStarCounter } from '@/components/github-star-counter'
import { HeroSimulation2 } from '@/components/hero-simulation-2'
import { MCPMarketplaceFeatures } from '@/components/mcp-marketplace-features'
import { PageContainer } from '@/components/page-container'
import { SupplySideCTA } from '@/components/supply-side-cta'
import { githubUrl, twitterUrl } from '@/lib/config'
-import {
- defaultConfig,
- getCodeForDeveloperConfig
-} from '@/lib/developer-config'
-import { globalAgenticApiClient } from '@/lib/global-api'
export default async function TheBestDamnLandingPageEver() {
- const projectIdentifier = '@agentic/search'
- const tool = 'search'
-
- const initialProject =
- await globalAgenticApiClient.getPublicProjectByIdentifier({
- projectIdentifier,
- populate: ['lastPublishedDeployment']
- })
-
- // TODO: this should be loaded in `ExampleUsage`
- const initialCodeSnippet = getCodeForDeveloperConfig({
- config: defaultConfig,
- project: initialProject,
- deployment: initialProject.lastPublishedDeployment!,
- identifier: projectIdentifier,
- tool
- })
- const initialCodeBlock = await highlight(initialCodeSnippet)
-
return (
- This example uses the{' '}
-
- {projectIdentifier}
- {' '}
- tool to provide an LLM access to the web.
-
- All Agentic tools are exposed as both{' '}
- MCP servers as well as simple{' '}
- HTTP APIs. MCP is important
- for interop and future-proofing, whereas simple HTTP POST requests
- make tool use easy to debug and simplifies integration with existing
- LLM tool calling.
-
- Agentic tools that{' '}
- work everywhere
-
-
-
Agentic tools are{' '}
@@ -98,6 +40,7 @@ export default async function TheBestDamnLandingPageEver() {
Agentic makes MCP fun!
diff --git a/apps/web/src/app/publishing/page.tsx b/apps/web/src/app/publishing/page.tsx
index 5641351b..a5cd5869 100644
--- a/apps/web/src/app/publishing/page.tsx
+++ b/apps/web/src/app/publishing/page.tsx
@@ -3,7 +3,7 @@ import Link from 'next/link'
import Zoom from 'react-medium-image-zoom'
import { DotsSection } from '@/components/dots-section'
-// import { ExampleAgenticConfigs } from '@/components/example-agentic-configs'
+import { ExampleUsageSection } from '@/components/example-usage-section'
import { GitHubStarCounter } from '@/components/github-star-counter'
import { MCPGatewayFeatures } from '@/components/mcp-gateway-features'
import { PageContainer } from '@/components/page-container'
@@ -59,30 +59,8 @@ export default function PublishingMCPsPage() {
- - Configuring your Agentic project - {' '} - is straightforward , regardless of whether your origin is an MCP - server or an OpenAPI service. For TS projects, you can use a - fully-typed agentic.config.ts{' '} - file, or fall back to using an{' '} - agentic.config.json file to - configure your project.{' '} - - Learn more - - . -
-+ This example uses the{' '} + + {projectIdentifier} + {' '} + tool to provide an LLM access to the web. +
+ ++ All Agentic tools are exposed as both{' '} + MCP servers as well as simple{' '} + HTTP APIs. MCP is important for + interop and future-proofing, whereas simple HTTP POST requests make + tool use easy to debug and simplifies integration with existing LLM + tool calling. +
+