apache.org valid
Apache Camel
Apache Camel is an open source integration framework with 350+ connectors for databases, APIs, message brokers, and cloud services. Write routes in Java, YAML, or XML. Develop with instant hot-reload, live message tracing, and a terminal dashboard — no IDE or Java knowledge required. Deploy on Spring Boot, Quarkus, or standalone. In production since 2007, used by thousands of companies worldwide. 83,000+ commits, 1,500+ contributors, median 1–2 day bug fix time. Apache License 2.0 — zero license
For agents: Apache Camel open-source integration framework with 350+ connectors; docs cover YAML/Java routes, MCP server and canonical examples.
integration frameworkenterprise integrationcamel routesconnectorsmcp server
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-23T00:03:23.369Z. Cached copy · Source on apache.org
# Apache Camel
> Apache Camel is an open source integration framework with 350+ connectors for databases, APIs, message brokers, and cloud services. Write routes in Java, YAML, or XML. Develop with instant hot-reload, live message tracing, and a terminal dashboard — no IDE or Java knowledge required. Deploy on Spring Boot, Quarkus, or standalone. In production since 2007, used by thousands of companies worldwide. 83,000+ commits, 1,500+ contributors, median 1–2 day bug fix time. Apache License 2.0 — zero license fees.
All Apache Camel documentation pages are available in LLM-friendly Markdown format by replacing `.html` with `.md` in any URL.
For example:
- HTML: `https://camel.apache.org/components/next/languages/simple-language.html`
- Markdown: `https://camel.apache.org/components/next/languages/simple-language.md`
Website pages have URLs that end in `/`; append `index.md` to read one as Markdown:
- HTML: `https://camel.apache.org/what-is-apache-camel/`
- Markdown: `https://camel.apache.org/what-is-apache-camel/index.md`
## Offline documentation bundles
For agents or environments with no or restricted internet access, versioned offline documentation bundles are available as zip archives of all Markdown files, one per documented Camel version:
- [Camel 4.22](https://github.com/apache/camel-website/releases/download/docs-4.22/camel-docs-4.22.zip)
- [Camel 4.18](https://github.com/apache/camel-website/releases/download/docs-4.18/camel-docs-4.18.zip)
Download the zip matching your Camel version, unzip it locally, and read the files from there. There is no bundle for `next` (the unreleased main branch): that documentation changes daily, read it online under `https://camel.apache.org/components/next/`. Each bundle contains:
```
components/<version>/ — 350+ connector/component docs (Markdown)
manual/ — user manual (Markdown)
what-is-apache-camel/, when-to-use/, trust/, camel-dna/
— the "Start here" website pages, as index.md
community/ — team, support, user stories, articles, books (index.md per page)
blog/ — every blog post as <year>/<month>/<post>/index.md; blog/index.md lists them
catalog/
components/ — 350+ connector/component metadata (JSON)
dataformats/ — data format metadata (JSON)
languages/ — expression language metadata (JSON)
models/ — EIP model metadata (JSON)
others/ — other component metadata (JSON)
schema/
camelYamlDsl-canonical.json — YAML DSL JSON Schema
llms.txt — this file
```
The `catalog/` JSON files contain machine-readable metadata for every connector/component, data format, language, and EIP — parameters, types, defaults, and descriptions. The YAML DSL schema is the definitive spec for validating and generating Camel YAML routes.
## Key facts
- Apache Camel is a **library**, not a platform — it embeds in your existing Spring
…
Related sites
Other listed sites in Infrastructure. See the whole category →
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| cloudflare.com | Cloudflare | interface AI and machine learning Cybersecurity +1 | 85 | ✓ | ✓ | ||
| workers.dev | Workers | documentation Infrastructure | 78 | ✓ | ✓ | ||
| ubuntu.com | Ubuntu | documentation Open source projects Infrastructure +1 | GB | 76 | ✓ | ✓ | |
| docker.com | Docker Documentation | documentation DevOps and observability Developer tools +1 | US | 75 | ✓ | ✓ | |
| fastly.net | Fastly | documentation Infrastructure | 75 | ✓ | |||
| opera.com | The Opera browser overview | documentation Infrastructure AI and machine learning +2 | NL | 74 | ✓ | ||
| cpanel.net | cPanel & WHM Documentation | documentation Marketing Documentation and reference +1 | US | 73 | ✓ | ||
| hostinger.com | Hostinger | interface Design Infrastructure +2 | 73 | ✓ | ✓ |
Machine-readable: GET /v1/resolve?q=apache.org · GET /v1/domain/apache.org · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage apache.org, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for apache.org:
1. POST https://agentwebmap.com/v1/sites/apache.org/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://apache.org/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/apache.org/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/apache.org).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.