Skip to main content

Official CENTCOM Python SDK for requests and webhook verification

Project description

centcom

Official CENTCOM Python SDK for human-in-the-loop approval requests and webhook verification.

Agent Integration Kit

To save time, give your coding agent this skill. It inspects your system, reports governance gaps, and suggests Contro1 integration (optional):

https://contro1.com/agent-kit

For LangGraph integration, use the companion package: centcom-langgraph.

Skill

This repo includes an integration skill:

  • skills/centcom-python-sdk.md
  • skills/contro1-eu-oversight.md
  • skills/contro1-us-ai-governance.md

Connector Repositories

Install

pip install centcom

Quick Start

import os
from centcom import CentcomClient, verify_webhook

client = CentcomClient(api_key=os.environ["CENTCOM_API_KEY"])
req = client.create_request(
    type="approval",
    context="Order #123 refund request",
    question="Approve refund?",
    callback_url="https://your-app.com/centcom-webhook",
    risk_level="high",
    policy_trigger="Refunds above $1,000 require manager review.",
    policy_context={
        "source": "custom_rules",
        "policy_name": "refund-controls",
        "rule_id": "refund-over-1000",
        "rule_reason": "Refunds above $1,000 require manager review.",
        "policy_version": "git:8f42c1a",
        "enforcement": "require_approval",
    },
    approval_comment_required=True,
    approval_policy={
        "mode": "threshold",
        "required_approvals": 2,
        "required_roles": ["manager", "admin"],
        "separation_of_duties": True,
        "fail_closed_on_timeout": True,
    },
)
print(req["id"])

For high-risk actions, callbacks are sent only after quorum is met, a reviewer rejects, or the request times out. Partial approvals are audit events and do not resume the agent.

Correlation and Routing

  • external_request_id = one external action idempotency key.
  • case_id (send as correlation_id) = broader business case that can contain multiple requests and audit records.
  • in_reply_to = direct continuation of a prior request or audit record.
  • POST /api/centcom/v1/requests/control-map previews role mapping, fallback reviewers, shift coverage, and policy satisfiability before request creation.

Policy evidence fields

Use these fields from any policy or risk source, not only a specific framework:

  • risk_level: low, medium, high, or critical.
  • policy_trigger: short human-readable reason review is required.
  • policy_context: evidence envelope with source, policy_name, rule_id, rule_reason, policy_version, and enforcement.
  • approval_comment_required: force reviewer justification even when risk is low or medium.

Contro1 does not need to own your policy engine. Your app, rules service, Microsoft AGT, OPA, Cedar, or custom code can decide that review is required; Contro1 handles routing, human decision, signed callback, and audit evidence.

Customer Agent Plugin Pattern

Build one small adapter in the customer orchestrator so agent prompts stay minimal and token-efficient:

class Contro1Plugin:
    def __init__(self, client):
        self.client = client
        self._control_map_cache = None
        self._control_map_ts = 0

    def preview_policy(self, payload, ttl_sec=300):
        now = time.time()
        if self._control_map_cache and now - self._control_map_ts < ttl_sec:
            return self._control_map_cache
        self._control_map_cache = self.client.preview_control_map(payload)
        self._control_map_ts = now
        return self._control_map_cache

    def request_human_review(self, *, title, context, case_id, action_id, **kwargs):
        return self.client.create_protocol_request({
            "title": title,
            "context": context,
            "external_request_id": action_id,
            "correlation_id": case_id,
            **kwargs,
        })

    def log_audit_action(self, *, action, summary, case_id, in_reply_to=None, **kwargs):
        return self.client.log_action(
            action=action,
            summary=summary,
            correlation_id=case_id,
            in_reply_to=in_reply_to,
            **kwargs,
        )

Quick Verify

python -c "import centcom; print('centcom installed')"

Related Packages

Ask a human

client = CentcomClient(api_key=os.environ["CENTCOM_API_KEY"])
thread_id = client.new_thread_id()

request = client.create_protocol_request({
    "title": "Approve vendor transfer?",
    "description": "Payment run 1024 wants to transfer funds to a vendor.",
    "request_type": "approval",
    "source": {"integration": "finance-agent"},
    "risk_level": "high",
    "policy_trigger": "Payments above $10,000 require finance approval.",
    "policy_context": {
        "source": "custom_rules",
        "policy_name": "finance-transfer-controls",
        "rule_id": "payment-over-10000",
        "rule_reason": "Payments above $10,000 require finance approval.",
        "policy_version": "git:8f42c1a",
        "enforcement": "require_approval",
    },
    "approval_comment_required": True,
    "continuation": {"mode": "decision", "callback_url": "https://agent.example.com/webhook"},
    "external_request_id": "payment:run_1024:approve",
    "correlation_id": "case_payment_run_1024",
})

Log an autonomous action

client.log_action(
    action="transfer.executed",
    summary="Transferred $500 to approved vendor account",
    source={"integration": "finance-agent"},
    outcome="success",
    correlation_id="case_payment_run_1024",
    in_reply_to={"type": "request", "id": request["id"]},
)

Use the same API key and base URL for both calls.

API

  • request(method, path, **kwargs), get(path, params=None), post(path, json=None), delete(path, json=None)
  • create_request(...), create_protocol_request(request), log_action(...)
  • preview_control_map(params), list_requests(...), get_request(request_id)
  • get_protocol_response(request_id), wait_for_response(...), wait_for_protocol_response(...)
  • get_request_evidence(request_id), get_thread(thread_id), get_trace(trace_id)
  • register_agent(...), list_agents(...), get_agent(...), get_agent_trail(...), get_agent_evidence(...)

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

centcom-1.1.0.tar.gz (19.9 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

centcom-1.1.0-py3-none-any.whl (14.2 kB view details)

Uploaded Python 3

File details

Details for the file centcom-1.1.0.tar.gz.

File metadata

  • Download URL: centcom-1.1.0.tar.gz
  • Upload date:
  • Size: 19.9 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.12.3

File hashes

Hashes for centcom-1.1.0.tar.gz
Algorithm Hash digest
SHA256 e1c3dcf942090ce80c4d15338fe0d66c9bd4ba59b4dd0465295752e2bb4e0429
MD5 b0d29bbc3dbe3fac9b70437a0d9b3e22
BLAKE2b-256 3cd67ad6495fef99bc457e6aec62b638bd066cf5b0c4bb6d2eeffef121362dc6

See more details on using hashes here.

File details

Details for the file centcom-1.1.0-py3-none-any.whl.

File metadata

  • Download URL: centcom-1.1.0-py3-none-any.whl
  • Upload date:
  • Size: 14.2 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.12.3

File hashes

Hashes for centcom-1.1.0-py3-none-any.whl
Algorithm Hash digest
SHA256 415f52723b7ae26f20a2fc3912f98894f9a75bb0fd9c3a039761cc873916a872
MD5 46a4640914de82028425bce913a31a73
BLAKE2b-256 a2604a26ebbc33f348343c864d714c0f123b0bd0fb9448c6ccf66ab308d28720

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page