meridian-governance-cli
Scriptable command-line client for Meridian Governance Router, over meridian-client. Installs as the meridian command.
Not to be confused with the unrelated meridian-cli package also on PyPI.
Not a chat REPL and not mta-cli with the serial numbers filed off —
Meridian doesn't have anything to chat with or a persona to pick. This is
closer in spirit to the aws or stripe CLIs: subcommands over an API,
scriptable, no interactive loop required.
Install
pip install meridian-governance-cli
Get credentials
meridian signup # new org — prompts for org name, email, password
# or
meridian login # existing account — authenticates, mints a new key
meridian whoami # confirm what's saved
Credentials live in ~/.meridian/config.json (mode 600 — api_key is in
there in plaintext, same tradeoff mta-cli makes for its own token). Override
the location with MERIDIAN_CLI_HOME if you want more than one profile.
Commands
meridian resolve my_agent [--project-id ID] [--json]
meridian explain ROUTING_LOG_ID
meridian audit ROUTING_LOG_ID --input-tokens N --output-tokens N
meridian projects create --name NAME [--quality Q] [--cost C] [--risk R]
meridian projects list
meridian agents create PROJECT_ID AGENT_NAME [--pinned-model M] [--quality-override Q] [--allowed-hubs h1,h2]
meridian agents list PROJECT_ID
meridian keys list [--json]
meridian keys create [--name NAME]
meridian keys revoke KEY_ID
meridian catalog
meridian logout
Every data-returning command without a dedicated human-readable format
(explain, audit, catalog, projects list, agents list) prints raw
JSON — pipe into jq.
What this deliberately doesn't do
- No chat, no persona selection, no device integrations — those are
mta-cliconcerns (consumer AI Companion), not Meridian's. Meridian answers "which model should this agent use"; it has nothing to converse with. - No hub/model/deployment registration commands — those routes aren't tenant-scoped today (console/house-key only), so a CLI command for them would just 403 for every real user. Added if/when that changes.
- No interactive REPL. If you want one, it'd be a thin layer calling the same
functions
cli.pyalready has — the commands are the primitive, not the shell.
Metadata
Release files for meridian-governance-cli 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| meridian_governance_cli-0.1.0.tar.gz | 7.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| meridian_governance_cli-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 15.1 kB
Release files / meridian_governance_cli-0.1.0.tar.gz
| Download URL | meridian_governance_cli-0.1.0.tar.gz |
|---|---|
| Size | 7.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
78ba2b3121dfb2574ddbed76bc3727d3aa44c8c141caf10a4765d379070e0e1e
|
|
BLAKE2b-256 checksum How to use checksums |
0156901af7ceab2277c6da08e11eb6067c4d66042b7c0d846ad58a4556807371
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / meridian_governance_cli-0.1.0-py3-none-any.whl
| Download URL | meridian_governance_cli-0.1.0-py3-none-any.whl |
|---|---|
| Size | 7.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cdda32b1f4b36b607ca4434033a0f7b1219f811c09adc3aa70bd2b7b68edae73
|
|
BLAKE2b-256 checksum How to use checksums |
b664675e59b8a09ad3b4b6805f992c902dab3192cf9200d6768c57b5a98a5dd7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for meridian-governance-cli 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.