Programmatic API

OpenTrust exposes its functionality through public static methods on OpenTrust_* classes rather than global functions. The signatures listed here are stable across the v1.x line.

Repository

Read-side data layer. The renderer and the chat corpus both go through this. Use it instead of raw WP_Query when you want OpenTrust's normalisation, locale handling, and "last updated" timestamps for free.

$repo = OpenTrust_Repository::instance();

Each fetch_* method returns an array of associative arrays. The shape mirrors the postmeta keys for that CPT, minus the _ot_ prefix, plus standard id, title, slug, permalink, updated_at.

$policies = OpenTrust_Repository::instance()->fetch_policies();
foreach ( $policies as $policy ) {
    printf(
        "%s - v%d (last reviewed %s)\n",
        $policy['title'],
        $policy['version'],
        $policy['review_date'] ?? 'never'
    );
}

Version control

Used internally by the policy save handler. Useful directly when you want to programmatically bump a policy version without going through the editor.

OpenTrust_Version::bump_version( $policy_id, 'Updated retention period from 24 to 36 months.' );

bump_version() runs synchronously and writes through wpdb directly for the version meta to avoid hitting the auto-summarizer cron more than once.

Catalogs

Read access to the bundled catalogs. The catalog filters (see Hooks) modify the data returned by these methods.

$entries = OpenTrust_Catalog::subprocessors();
$matches = array_filter( $entries, fn( $e ) => str_contains( strtolower( $e['name'] ), 'aws' ) );

Secrets

libsodium-encrypted secret storage. Use this when you want to store an additional secret alongside OpenTrust's keys (e.g. a webhook signing secret) under the same AUTH_KEY-derived encryption.

OpenTrust_Chat_Secrets::set( 'webhook', $signing_secret );

// Later:
$key = OpenTrust_Chat_Secrets::get( 'webhook' );
if ( false === $key ) {
    // AUTH_KEY rotated. Re-prompt for the secret.
}

Budgets and rate limits

Reserve-commit-release token accounting plus sliding-window rate limits.

The check-and-reserve pattern is what prevents two concurrent requests from each thinking they can spend the last 1000 tokens.

Chat log

Programmatic access to wp_opentrust_chat_log.

Import / Export

Programmatic access to the IO archive format.

$strategy is one of OpenTrust_IO::STRATEGY_SKIP, STRATEGY_OVERWRITE, STRATEGY_CREATE_NEW.

Corpus

Build, cache, and invalidate the AI chat's corpus.

If you ship a custom chat surface that calls the REST endpoint, you do not need to touch the corpus directly. It's invalidated automatically on every CPT save. Direct access is useful for diagnostic tooling.

Core utilities

Colour math and other utilities that don't fit elsewhere.

Cache invalidation hook (internal but useful)

OpenTrust_CPT::register_invalidator(array $cpts, callable $cb) lets you wire a callback to all four cache-busting events for a list of CPTs (save, delete, trash/untrash, transition_post_status) in a single call. This is how OpenTrust keeps its render cache and chat corpus aligned with content changes.

OpenTrust_CPT::register_invalidator(
    [ 'ot_policy', 'ot_certification' ],
    function ( $post_id, $event ) {
        // Your custom invalidation here.
    }
);

The callback receives $post_id and an $event string identifying which lifecycle event fired. Useful for syncing OpenTrust content into your own search index or analytics pipeline.