Skip to content
PharoHome

How Pharo works

Pharo turns a business’s approved website information into a maintained public profile that people and AI agents can read. The business controls which release is published; having a publicly accessible website alone does not authorize publication.

Connect owned sources

A business verifies control of its website hostname and selects source pages. Hostname verification establishes control of that address, not legal ownership of the business. Owner-provided Markdown and text are supported where document inputs are enabled; they are currently disabled on this hosted instance.

Publish source-linked knowledge

An approved release contains a readable profile, structured facts, page-level source references and machine-readable files. Published facts can be traced back to their sources and to a release snapshot. Private prospect reports and unpublished documents stay outside this public surface.

Ask, with clear limits

The published profile can answer questions with citations. When approved sources do not support a detail, the response reports an unknown outcome instead of supplying an unsupported claim. Source quality and freshness still matter, so businesses should review and update their information.

Illustrative profile

This fictional example explains the behavior; it is not a published customer or a live API response.

Example source: “The Lantern Bakery opens Tuesday to Saturday, 08:00–16:00.”

Question: “When is the bakery open?” Answer: “Tuesday to Saturday, 08:00–16:00,” with a citation to that source.

Question: “Does it offer delivery?” Outcome: Unknown, because the example source does not say.

See how agents access published profiles and how the ProfileReader crawler handles websites.