15Contact

Product questions, integration support, research discussion, and responsible issue reporting

Bring us the question behind the signal.

Talk with Insight about oracle evidence, risk interpretation, API access, or production integrations. Choose the channel that best matches the work.

01Private by email
02Public issue trail
03Open resources

Conversation path03 / 03

Choose a routePrivate · public · updates
Show the evidenceEndpoint · asset · receipt
Continue the threadReply · issue · resolution

01 — Choose the conversation

Send private account or integration context by email. Keep reproducible product issues in GitHub so others can follow the technical record. X is for updates.

C—01Private conversation

Email

Account context, integrations, partnerships, and sensitive reports.

contact@oracleinsight.xyz

Compose an email

C—02Public technical record

GitHub

Reproducible bugs, documentation corrections, and contributions.

github.com/imokokok/Insight

Open repository

C—03Updates & research

X (Twitter)

Follow product releases and oracle risk research in public.

@imokokok27

Follow updates

02 — Make the signal actionable

A little context helps us reproduce a problem or interpret the evidence without another round trip.

MESSAGE BRIEF

What to include

01
The surface — product page, API endpoint, or integration.
02
The evidence — asset, provider, chain, time, or receipt ID if relevant.
03
The gap — what you expected and what you observed.