World Agent Web (WAW) is an ecosystem of protocols for AI agents to discover and interact with web services through standardized manifests.
WAW fills a specific gap: standardized discovery and invocation of web services for AI agents. Existing protocols serve different purposes (see COMPARISON.md).
Currently in proof-of-concept phase. Seeking community validation before production recommendations.
They're complementary:
- MCP: Desktop apps, local tools
- WAW: Web services, HTTP-based
See COMPARISON.md for detailed comparison.
- Create agent manifest JSON
- Add
/agent-manifest.jsonendpoint - Optionally adapt endpoints for WAW format
- Test with reference client
Reference implementation is Python. Community contributions welcome for other languages.
No. WAW can wrap existing APIs. Just add manifest and optionally create WAW-compliant endpoints.
WAW supports multiple auth methods: None, API Key, OAuth2, JWT. Services choose what fits their needs.
Simplicity and universal support. JSON works everywhere without code generation.
Broader compatibility. Can work with HTTP/2 transparently.
Yes. Services should set appropriate cache headers.
Services implement their own rate limiting. Standard HTTP 429 responses.
Security depends on implementation:
- Use HTTPS in production
- Implement authentication
- Validate all inputs
- Follow security best practices
- Rate limiting
- Authentication/authorization
- Input validation
- Monitoring and logging
Services must comply with applicable laws (GDPR, CCPA). Manifests should link to privacy policies.
Different goals. GraphQL: flexible querying. WAW: agent discovery.
gRPC: high performance. WAW: simplicity and discoverability.
OpenAPI: human documentation. WAW: agent integration.
- Provide feedback on WAW
- Test with your services
- Report bugs
- Contribute examples
- Improve documentation
See CONTRIBUTING.md.
Yes. MIT license allows commercial use.