Community — Agentic Web Protocol

CONTRIBUTING.md
# Contributing to AWP

## Running locally
git clone https://github.com/QueryXLabs/agentic-web-protocol-private-
cd agentic-web-protocol-private-
npm install
npm run build        # Build all packages
npm run test         # Run all tests
npm run test:python  # Python SDK tests

## Submitting a PR
1. Fork the repo
2. Create a feature branch: git checkout -b feat/my-feature
3. Write tests for your changes
4. Run npm run verify:all (must pass)
5. Submit PR with a clear description of the change

Good first issuesCheck GitHub issues labeled good first issue for beginner-friendly contributions.

Bounty Program

The AWP Adoption Fund pays bounties for high-value ecosystem contributions. All bounties are paid in USD via GitHub Sponsors or direct transfer upon PR merge.

TaskRewardDifficulty

WordPress plugin publish to .org$500Medium

Shopify App Store submission$750Hard

Ruby on Rails SDK$400Medium

PHP SDK (standalone, no WordPress)$350Medium

Go SDK$400Medium

Add AWP support to Astro framework$300Easy

Token savings benchmark suite$200Easy

Federation manifest spec + reference impl$1000Hard

To claim a bounty: open an issue, get approval from a maintainer, submit your PR, and it will be paid upon merge. Email bounties@agentwebprotocol.dev.

Governance

AWP uses a lightweight RFC process for protocol changes. All RFCs are public, have a 2-week comment window, and require core team consensus.

GOVERNANCE.md
# AWP Governance

## Decision Making
- RFC (Request for Comments) process for protocol changes
- 2-week public comment period for all RFCs
- Core team votes on RFCs after comment period
- Breaking changes require 2/3 supermajority

## Core Team
- Protocol design and schema ownership
- TypeScript and Python SDK maintenance
- Docs site and tooling
- Marketplace moderation

## Working Groups
- WG-Security: threat model and auth standards
- WG-Integrations: CMS, e-commerce, and platform partnerships
- WG-Agents: agent-side consumption patterns and best practices

RFC Example

RFCs live in rfcs/ and follow this template:

rfcs/0001-function-schemas.md
# RFC-0001: AWP Function Schemas

## Summary
Standardize how agent-callable functions are declared in AWP manifests.

## Motivation
Agents need a machine-readable way to discover and invoke site operations.
HTML forms and prose documentation are insufficient.

## Proposal
Add a `functions` array to the site manifest:

{
  "functions": [{
    "name": "search_products",
    "description": "Search the product catalog",
    "method": "GET",
    "path": "/api/v1/products",
    "parameters": { ... }
  }]
}

## Alternatives Considered
- OpenAPI inline embedding (too verbose for token budgets)
- MCP-only approach (limits non-MCP agents)

## Status: Accepted

RFC statusAll accepted RFCs are tracked in the rfcs/ directory.