Connect Ordinal to Codex
Give Codex governed access to Ordinal’s 50 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Ordinal to Codex in four steps
Admins approve the server once. Everyone in Codex then gets it through the same governed connection.
- 1
Approve Ordinal in Runlayer
Add Ordinal from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Codex to Runlayer
Runlayer’s CLI adds the Runlayer Plugin to Codex’s local plugin marketplace, and users then enable it in Codex. With direct tool listing turned on for your deployment, Ordinal’s 50 tools show up in Codex’s own tool list (Codex 0.122 or newer, installed through the Runlayer CLI).
Codex setup guide - 3
Sign in to Ordinal
An admin adds Ordinal credentials to Runlayer once. They never sit in the client’s configuration.
- 4
Use Ordinal from Codex
Ordinal’s approved tools appear in Codex. Every call is checked against policy and recorded.
Tools
50 Ordinal tools in Codex
Runlayer policy decides which of these Codex users can call.
Get analytics cpm
Get CPM Values - Retrieve the current CPM (Cost Per Mille) values used for EMV calculations across all platforms.
Update analytics cpm
Update CPM Values - Update the CPM values used for EMV calculations.
Analytics linkedin followers
Retrieve follower count history for a LinkedIn profile.
Analytics linkedin posts
Retrieve post analytics for a LinkedIn profile within a date range.
Analytics x followers
Retrieve follower count history for an X profile.
Analytics x posts
Retrieve post analytics for an X profile within a date range.
Create approvals
Create one or more approval requests for a post.
Delete approvals
Delete an approval request.
Control
What Runlayer can see and stop in Codex
Some controls apply to every client at the gateway. Others depend on what Codex exposes to Runlayer.
Gateway policy (available)
Every Ordinal call from Codex passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Codex as the client, the tool, and the policy and scanner decisions.
Client hooks (available)
Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.
Stop a call before it runs (available)
Runlayer can deny a tool call or permission request before Codex runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before Codex’s model sees it.
Redact output in place (not available)
Codex cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.
Frequently asked questions
Connect more