ParcelClear, described for machines.

Read the statute pages. Each one covers a path a Texas closing takes: the affidavit and the three underwriter paths, entity and trust buyers, leases of twelve months or more, mineral and royalty interests, and OFAC screening at a closing.

Read the state land-law pages for Florida, Indiana, Arizona, and Arkansas. Those pages describe the statute. Only Texas has a live Record. The Florida Record is building and is not for sale.

Read the sample record. It is a watermarked PDF of a finished record for an individual buyer who is a United States citizen, with no potential matches, so its hits and dispositions section reads "No hits recorded".

Read the second sample for the other path. An entity buyer whose control person is a true match, which is the shape that fills the hits and dispositions table: a match a reviewer confirmed with a written reason, a candidate a reviewer looked at and dismissed, and one the system dismissed on its own below the display threshold. Both are watermarked, both use fictional names and a fictional hash, and neither is a record or can be verified.

Read the plain-text index and the full text of every page if parsing HTML is not worth it. Both are generated from the copy these pages render, so they say the same thing this page does.

Read the RFC 9727 catalog. It lists those same read-only documents and a machine description of them. There is no API and no agent checkout.

Read auth.md if you are looking for agent registration. There is no registration endpoint. The Protected Resource Metadata and Authorization Server metadata repeat that: the read scope is GET of public documents, and there is no token to mint.

Read the A2A Agent Card. It lists those same read-only documents as skills. There is no API and no agent checkout. This host does not accept A2A tasks.

Read the Agent Skills index. The listed skill is GET of public documents. There is no API and no agent checkout.

There is no MCP server on this host. The Server Card is the discovery document that says so.

This page registers read-only browser tools for search, navigation, and reading published documents when the browser supports them. There is no MCP server and no agent checkout.

DNS-AID is published at _index._agents.parcelclear.com and points at this site. There is no API and no agent checkout.

Read the HTTP Message Signatures Directory. It publishes the Ed25519 public key this host uses to sign outbound fetches. There is no API and no agent checkout.

Request any public page with Accept: text/markdown to receive that page as Markdown. HTML stays the default for browsers. That is content negotiation on the same URL, not an API.

Send a human to the pricing page to buy a record with a card. There is no API and no agent checkout today. No endpoint on this site accepts an order or returns a record, and there is no MCP server.

There is no API to build against, but if you are building something that would use one, say so at support@parcelclear.com. That address is where the request gets counted; nothing here promises anything back.

The questionnaire answers, as the party attested them.

The party list, with the role and the party type of each one.

The control-person tree for an entity or trust buyer: every control person by name and role, the control tests each one meets, and the statement by the reviewer that the tree is complete from the documents in the file.

The screen result for every name against the OFAC SDN and Consolidated lists, with the list version id and the date that list was fetched.

The rule set id and version that evaluated the answers.

The result the rule set returned, and the id and reason of every rule that fired.

The disposition a reviewer recorded on each potential match, with the written reason.

The SHA-256 of the evidence pack PDF, and the public verification URL for that hash.

These are the words a record uses for its outcome. They are read from the active rule set rather than restated here, so a version bump moves them.

Missing facts, a list older than seven days, or a screen that does not complete produce HOLD. A record never returns a passing result when it could not finish the work.

The rules are data with a version, not code. Every record is pinned to the version that evaluated it, and a finalized record keeps that version after a newer one ships.

Rule-set hashes from tx-sb17 1.0.4 forward are computed over canonical JSON, with object keys sorted and whitespace removed, so the same rule set hashes the same after reformatting or a database round trip, and the value can be recomputed from the stored rule set with scripts/verify-rules.ts.

The rule set is published in full below. Every rule id a record prints, every reason string, and every control-person test id resolves in that file, and the hash above is the canonical hash of it.

The fields the questionnaire collects, their types, and the two a record cannot be created without, as JSON Schema draft 2020-12. It is generated from the same field list the form renders, so a field added to the rule set appears in both.