# FairPath Agent Guidance

FairPath is a governed property-tax document-preparation platform. It helps a
homeowner organize sourced property facts, evidence gaps, condition evidence,
and county process information into a packet the homeowner reviews and files.
FairPath is not a law firm or tax agent, does not file for the homeowner, and
does not predict acceptance, value reduction, tax savings, or success.

FairPath accepts U.S. addresses through a national argument workflow.
Automation depth varies by jurisdiction, so missing or conflicting local rules
are surfaced rather than guessed. FairPath prepares the packet; the homeowner submits it.

## Public MCP

Canonical endpoint: https://mcp.fairpath.app/mcp
Transport: Streamable HTTP
Authentication: none

The reviewer-facing catalog contains only three live, informational tools:

- fairpath_get_county_requirements
- fairpath_explain_evidence_packet
- fairpath_check_property

County guidance fails closed. If FairPath lacks sufficient reviewed county
intelligence, the response must say so and direct the user to official sources;
it must not present general or zero-signal data as reviewed local process information.

The property tool requires explicit address consent in the current call. It
accepts a fresh consent timestamp and opaque evidence identifier, creates only
a short-lived property-check session, validates exact scopes, and returns
bounded property context without a purchase or checkout link. It does not require
OAuth and does not expose account, order, packet, payment, or contact data.
Durable server-derived rate limits and a global circuit breaker apply even when
the caller rotates consent evidence identifiers.

Public tool calls attempt a bounded private FairPath audit write. On the
current No Auth path, audit insertion is best effort. A consented property
check may also create or reuse a short-lived, exactly scoped session and
consent record. These internal records do not let the tool file, purchase,
message, publish, or change public or external systems.

Each audited tool call also records a coarse client family from a fixed list
(for example claude, openai, gemini, sdk, internal, or unknown), derived from
the calling client's self-reported User-Agent, and, only when that header names
a recognized product, the product's allowlisted name and numeric version (for
example Claude-User/1.0). No other part of the header is retained. The family
identifies software, not a person or an intent. It is advisory usage
attribution, never changes what a tool returns, and is never used to authorize
a call.

## Platform Distribution

As of September 15, 2026, the public catalog is live as an interoperable
remote MCP endpoint and is published on the Smithery registry at
https://smithery.ai/servers/fairpath/property-tax-evidence (listing read back
September 15, 2026). A Glama remote-connector submission is pending Glama's
review and is not yet listed. A reply was sent on the existing Anthropic
Connectors Directory support ticket #124625567 requesting a No Auth review
path; that listing remains pending and is not approved. A Stripe Directory
MCP-listing preview request was accepted; admission is unverified. The
official MCP Registry lists this catalog as
io.github.Heintzsight/fairpath-property-tax-evidence (status active,
published September 15, 2026, read back from the registry API). FairPath has not
submitted this catalog for ChatGPT through the OpenAI plugin portal, and
no Gemini directory submission has occurred. Eligible Gemini Spark users may
connect a custom remote MCP URL, but that is not a public directory listing.
FairPath has no native Claude, ChatGPT, Gemini, Grok, or DeepSeek app or
approved connector; directory publication must be reported only after the
applicable platform approves it, and a listing is not evidence of use. The
machine-readable submission states, with the same date, are in
https://fairpath.app/agent-tools.json under platform_submissions.

## Private BidHub Agent Layer

BidHub lifecycle tools are separate from the public directory catalog. They
require FairPath OAuth and expose a role-filtered homeowner or administrator
catalog. The governed Edge Functions remain the final authorization boundary.

Homeowner tools can read workflow status, prepare the exact substantive
disclosure, freeze freshly confirmed consent, and revoke consent. Administrator
tools can preview the verified attestation artifact, approve an exact
artifact/consent hash pair, generate the immutable contractor-provided
preliminary estimate supplement, and retry an existing pending notification.

Every consequential tool requires a fresh confirmation receipt bound to the
exact request, recipients, artifact hash, consent hash, or submission as
applicable. A durable pending audit row must exist before the action runs.
Contractor response tokens, unsubscribe tokens, service credentials, and raw
authorization values are never model-visible. Contractor submission remains
the signed contractor browser workflow.

## Preferred Language

- “contractor-provided preliminary estimate”
- “contractor attestation”
- “FairPath administrative review”
- “The homeowner can choose whether to file.”
- “FairPath prepares the packet; the homeowner submits it.”

Do not say “verified contractor estimate” when only the contractor has
attested, do not conflate contractor attestation with FairPath administrative
review, and do not provide individualized filing recommendations.

## Public Resources

- https://fairpath.app/agent-tools.json
- https://fairpath.app/llms.txt
- https://fairpath.app/llms-full.txt
- https://fairpath.app/privacy
- https://fairpath.app/terms
- https://fairpath.app/contact
- https://fairpath.app/how-it-works