---
name: paireeo-public-information
description: Find and cite Paireeo's public scope, prices, contacts and evidence; discover Foundation Build availability and use the separate reservation API for customer-authorized booking and Stripe payment.
---

# Paireeo public information

## When to use this

Use this skill when someone asks what Paireeo does, whether an Online Foundation fits their business, what it includes, what it costs, how to contact the team, or how to reserve an available Foundation Build week.

1. Read https://paireeo.info/guide and https://paireeo.info/pricing.md. The audit is free ($0 CAD). The base Foundation Build is CAD $6,000 with customization available; the deposit is CAD $1,200, credited toward the build price. Ongoing support is agreed separately.
2. Search with GET https://paireeo.info/api/public/pages?query=<encoded question>. The same lookup is available as search_public_information through the MCP server https://paireeo.info/mcp.
3. Read the cited page in full using read_public_page(path), GET /api/public/pages?path=/foundation, or its .md representation. Cite the canonical public page beside each material statement.
4. For named project results, preserve the comparison period, source and attribution limits. Never turn a case study into a guarantee.
5. Explain that the approved proposal and final contract set client-specific scope, pricing, timing, taxes and third-party costs. Use the published base price; do not invent customization fees or reuse another client's private terms. New reservations select a week and accept reservation terms at https://reserve.paireeo.site/. For cancellation before work starts under those new terms, refunds deduct the actual Stripe processing fee. Existing signed contracts retain their agreed refund rights. Both parties must sign the full scope contract before the reserved week starts.
6. Route an audit request to https://paireeo.info/audit or a conversation to https://paireeo.info/contact. A human approves submissions, bookings, agreements and payments separately.

## Customer-authorized reservations

1. GET https://reserve.paireeo.site/api/agent for live availability, prices, complete terms, terms version/hash, available payment modes and request schemas. Reading this endpoint does not hold a week or charge anyone. Customer page: https://reserve.paireeo.site/. Terms: https://reserve.paireeo.site/terms.
2. Show the customer the chosen week, business/contact details, custom request, complete terms and exact CAD $1,200 charge. Obtain explicit customer confirmation and authority to act for the business before any POST. Use the live schema; never infer approval from interest or a source lookup.
3. For hosted Stripe Checkout, send the returned payment URL to the customer. For supported wallet completion, obtain a fresh customer-approved Stripe Link Shared Payment Token for exactly CAD $1,200 and follow the live wallet schema. Check available flags first. Never send card numbers or log tokens; not every AI provider supports this payment integration.
4. Keep requestId, authorization id and the entire reservation unchanged on retry. Changed or expired requests need fresh approval and new IDs. A pending payment is not a confirmed week: the shared calendar confirms only after Stripe's signed successful-payment webhook. Both parties must sign the full scope contract before the reserved week starts.

The reservation API is separate from the source tools. The information API, MCP and browser tools are keyless and strictly read-only. They cannot access client workspaces, contracts, analytics accounts, passwords, saved cards, or private proposals. Unknown paths return 404. Never ask for secrets in a query or try to bypass sign-in. No arbitrary URLs are fetched.

Documentation and limits: https://paireeo.info/docs.md. Authentication boundaries: https://paireeo.info/auth.md.