# Institutional Verification Publisher API

**URL:** <https://community.perplexity.ai/t/institutional-verification-publisher-api/6458>\
**Category:** Feature Requests\
**Tags:** api\
**Created:** [November 2, 2026, 2:24am UTC](https://community.perplexity.ai/t/institutional-verification-publisher-api/6458 "2026-11-02T02:24:42Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![manifoldgrace](https://sea1.discourse-cdn.com/flex001/user_avatar/community.perplexity.ai/manifoldgrace/32/3760_2.png) [@manifoldgrace](https://community.perplexity.ai/u/manifoldgrace)\
**Post date:** [November 2, 2026, 2:24am UTC](https://community.perplexity.ai/t/institutional-verification-publisher-api/6458/1 "2026-11-02T02:24:42Z")

</div>

**Prepared 2 November 2026 · Grace R. Nettey · Manifold Grace**

Reference foundation: [Interoperable Institutional Evidence Verification API with Provenance Tracking](https://community.perplexity.ai/t/interoperable-institutional-evidence-verification-api-with-provenance-tracking/6457)

* * *

# Institutional Verification Publisher API

## Pre-flight checklist

- This is an API feature request, not a consumer app or Comet UI request.
- Check current documentation and forum topics for closely equivalent functionality before posting.
- The developer workflow or API use case is described below.

## Feature type

New endpoint or API capability; New response field or metadata

## Affected API area

Search API; Agent API

## Summary

Institutions need a structured way to publish reviewed, claim-specific verification records for retrieval by AI applications.

## Problem

General search and document ingestion do not by themselves define who attested to a claim, what was checked, or which excerpts are permitted for public reuse.

## Proposed API behavior

Offer an opt-in publisher workflow: authenticated publisher registration; claim-specific submission; human review metadata; scoped publication approval; signed, versioned public records; and a read-only discovery endpoint. Keep underlying restricted documents private. Proposed fields: claim\_id, issuer\_id, claim\_text, evidence\_basis, reviewed\_at, allowed\_scope, status, version, limitations, citations.

## Example usage

A regulator publishes a reviewed finding with a permanent record ID. A Perplexity-powered research tool retrieves its public evidence summary, review scope and source URL without gaining access to confidential exhibits.

## Workarounds tried / considered

Document hosting, search indexing and custom external tool adapters can expose content but need application-specific publisher, consent and verification workflows. This is a design assessment, not evidence of a completed implementation.

## Impact

Institutional publishers, API developers and users benefit from controlled disclosure, traceability and reusable reviewed records.

## Additional context

Proposed as a focused publishing layer complementing my 2 November 2026 Perplexity evidence-verification architecture. This is not a claim that publisher identity systems or signed records are new.

**Proposal attribution:** Grace R. Nettey — Manifold Grace. Human-led conceptual research, with AI assistance in structuring and drafting. The request invites consideration; it does not demand implementation.

**Related foundation:** [Interoperable Institutional Evidence Verification API with Provenance Tracking](https://community.perplexity.ai/t/interoperable-institutional-evidence-verification-api-with-provenance-tracking/6457)