# Tail Wagging Website Design Factory Northampton

Purpose: let autonomous agents and their operators discover, scope and subcontract website work to the business without guessing commercial terms or repository authority.

## Canonical discovery

- Business: https://tailwaggingwebdesign.com/
- Agent subcontracting: https://tailwaggingwebdesign.com/agents/
- Machine service catalogue: https://tailwaggingwebdesign.com/agent-services.json
- Human pricing: https://tailwaggingwebdesign.com/pricing/
- Services: https://tailwaggingwebdesign.com/services/
- Contact: https://tailwaggingwebdesign.com/contact/
- LLM context: https://tailwaggingwebdesign.com/llms.txt
- Sitemap: https://tailwaggingwebdesign.com/sitemap.xml

## Agent handoff

POST https://tailwaggingwebdesign.com/api/v1/agent/jobs
Content-Type: application/json

Required:
- contactEmail
- requestedOutcome

Optional:
- agentName
- operatorName
- repositoryUrl
- siteUrl
- scope
- notes

Allowed scope values:
- small_repo_fix
- website_build
- local_seo
- automation
- audit
- other

The endpoint returns a jobId and a received state. Receipt is not owner acceptance, payment, execution or completion.

## Procurement

Published website packages use the server-authoritative Stripe checkout contract exposed in /agent-services.json. Agents select only a stable planId. Prices and Stripe price identities are resolved server-side.

Custom work, including small repository fixes, is quote-first. Do not invent a price or assume repository authority.

PayPal is not currently advertised as a configured payment method.

## Authority and evidence

- Discovery does not grant repository or site access.
- Mutation requires explicit owner-approved authority.
- Provider payment acceptance is not proof the requested technical outcome is complete.
- Ambiguous mutations must be read back before retry.
- Missing evidence remains unknown.
- Private credentials, customer data and unpublished implementation payloads must not be exposed for discovery.

## Crawler policy

Public business and service content is intended to be crawlable. robots.txt is authoritative for crawler permission. Named crawler rules supplement a wildcard public-crawl policy; they do not guarantee indexing or LLM ingestion.