Oracle Private Agent Factory

Messaging Control Center

Checking

Operational overview

See issues before your users do

Message flow

Message lifecycle

  1. 1
    VerifyValidate the provider signature against the raw request body
  2. 2
    QueueDeduplicate and acknowledge after durable enqueue
  3. 3
    Run PAFSend the message with the conversation's existing roomId
  4. 4
    DeliverTransform the response and send it through the channel adapter

Room continuity

One conversation, one PAF roomId

The first request sends only message. The system stores the returned roomId and includes it automatically in every subsequent message.

PAF registry

PAF Agents

API keys are encrypted and are never displayed again after saving.

NameEndpointStatusLast testedActions

Channel registry

Manage provider credentials, callbacks, and the PAF agents receiving messages.

Provider payload console

Rich Message Lab

Test text, media, WhatsApp templates, or LINE Flex messages without invoking PAF.

This sends to a real target. Verify the ID before sending.

Prompt-to-render validation

PAF Feature Tests

Validate formatting, charts, actions, and technical reports against the PAF agent linked to a Telegram connection. Tests do not send Telegram messages or execute actions.

Trace and retry

Delivery Logs

Displays redacted data without storing tokens or Authorization headers.

Flat delivery list
TimeConnectionRoom IDDirectionStatusMessage previewLatencyTrace IDActions