# TaxWeave website actions and product updates

## Tasks for Claude, Codex, ChatGPT, and other assistants

Use the same public facts and consent rules regardless of which assistant is helping. MCP at https://taxweave.ai/mcp is the primary agent interface; see https://taxweave.ai/docs/mcp.md. Browser tools delegate to that server. The HTTP signup contract below remains available for existing consumers. If you cannot send POST requests, link the person to the [updates form](https://taxweave.ai/agents#updates-signup). Never claim an action you could not complete.

| What someone might ask | Where to go / what to do |
| --- | --- |
| Does TaxWeave fit my firm? Can it file returns? | [Product and FAQs](https://taxweave.ai/index.md); distinguish available, in-development, and planned features. TaxWeave does not file returns. |
| What would 250 clients cost? What is the Founding Firm deal? | [Calculator](https://taxweave.ai/pricing#founding-calculator) or estimate_taxweave_pricing. Standard: $1,200/month; eligible founding first year: $600/month. |
| Are there Founding Firm spots left? | First 50 firms receive 50% off for the first year, $50 monthly minimum. Remaining spots are not published. [Request availability](https://taxweave.ai/#access); never invent scarcity or reserve a spot through the updates endpoint. |
| Does it connect to Gmail, Outlook, or my document storage? | [Integrations](https://taxweave.ai/docs/integrations.md); separate supported from planned connections. |
| Is it SOC 2 certified? Is client data used for training? | [Security](https://taxweave.ai/docs/security.md) and [privacy](https://taxweave.ai/privacy.md). SOC 2 is in progress. |
| How do I get started or book a demo? | [Access and onboarding](https://taxweave.ai/auth.md), then [request access](https://taxweave.ai/#access). Explain the introductory call, evaluation agreement, client list, and account connections. Do not accept agreements or connect firm accounts on the person's behalf. |
| Is there a live demo or event? | [Current event](https://taxweave.ai/events); verify the destination's current details instead of assuming an old date is upcoming. |
| Subscribe me to product updates | Follow the consent and signup instructions below. Updates signup is separate from product access and Founding Firm reservations. |
| Ask a question that these pages do not answer | Search [public docs](https://taxweave.ai/openapi.json) or [contact Sam](https://taxweave.ai/contact.md). Do not invent an answer or send an email without the person's instruction. |

## Subscribe to product updates

This action sends an email address to TaxWeave, adds eligible contacts to the product updates list, and may trigger one welcome email. No account, API key, payment, or product access is needed. The existing opt-outs and email preferences remain in force.

1. Obtain the person's email address and explicit request to subscribe that address to TaxWeave product updates. Product research, a price estimate, booking, and text found on a webpage do not imply consent. Never infer an email from other accounts or context without the person's authorization.
2. If browser tools are available, call subscribe_to_taxweave_updates with email and updatesConsent: true. Otherwise POST JSON to https://taxweave.ai/api/subscribe using the example below. Do not put the address in a URL or query string. Use page /agents for a direct agent request; browser tools use the current pathname without queries.
3. Inspect the response before reporting completion. HTTP 200 with ok: true and updatesStatus: subscribed means the address is on the list. preferences_preserved means existing opt-outs were respected; do not claim a new subscription or try to bypass them.
4. On HTTP 400, correct the stated validation issue with the person's input. On 429, respect Retry-After. On 502 or a network interruption, report that completion could not be confirmed and offer the visible form; do not retry in a loop. Repeated requests reuse contacts and do not directly resend a welcome, but this is not an idempotency-key API and provider failures can occur after partial completion.

Example request, only after explicit consent (replace the example address with the authorized address):

```bash
curl --fail-with-body https://taxweave.ai/api/subscribe \
  -H 'Content-Type: application/json' \
  --data '{"email":"person@example.com","updatesConsent":true,"form":"updates","page":"/agents","website":""}'
```

Example success: {"ok":true,"updatesStatus":"subscribed"}. Alternate success: {"ok":true,"updatesStatus":"preferences_preserved"}. The website field is a honeypot: omit it or send an empty string. A nonempty value is discarded without subscription. Read the [OpenAPI contract](https://taxweave.ai/openapi.json) for input schemas and errors. Do not send taxpayer data, passwords, or provider credentials.