This deployment serves one enforced vertical and one public audience. Its configured boundary defines what the search can return.

• Boundary

  A visitor may narrow the configured scope but cannot escape it.

• Allowance

  Anonymous use runs under a lower rolling allowance. Registered use runs under the person’s plan.

• Automation

  Automated collection through the public interface is not permitted. Automated access belongs in the published REST service.

Results display a title, snippet, domain and date. Admitted material is stored and indexed once, then made available to every search in this instance.

• An unvalidated policy combination fails closed and remains visibly blocked. It is never silently admitted.
• Login, paywall and CAPTCHA controls are never bypassed.
• Unavailable evidence is never replaced with a different source or unsupported text.

Service access requires a scoped key sent as a bearer token. Keys are hashed at rest and cannot be recovered after creation.

• One accepted enriched search consumes one unit. A retry with the same idempotency key does not charge twice.
• Consumption is recorded in a metered ledger. Plan caps are hard and automatic overage is disabled, so a request at the cap is refused rather than charged.
• A service key may be revoked. The published REST contract is the service; MCP is a possible future wrapper and is not promised here.

Sponsored inventory is always labeled and occupies space separate from organic results. Payment cannot alter organic order, and organic position is never sold.

• Targeting is contextual to the query, active lens and domain. It does not use a person’s profile or search history.
• Advertiser reporting is aggregate. Creatives are reviewed, and a rejection states its reason.
• Charges apply only to documented events. No rate is published here because inventory pricing is set by this deployment’s operator.

The following uses are not permitted.

• Attempting to bypass an allowance, a plan cap or a service-key scope.
• Collecting automatically through the public interface instead of the REST service.
• Attempting to influence organic order by any means.
• Misusing the report path.

Abuse limits apply per account, per key and per network address. A limited request is refused with a declared state.

Anyone may report a result or request a correction, and a source may object to its treatment.

1. AThe request is recorded with its evidence.
2. BThis deployment’s staff adjudicates it, and the decision remains auditable.
3. CA granted correction can propagate a remeasurement to the index.

A report does not guarantee an outcome.

These terms are versioned. The version in force is the one published here, and material changes are published on this page.

Version

not configured

Effective date

not configured