CurbiCurbi
CURBI POLICY STUDIO / LOCAL WORKBENCH

From idea.
To a working check.

Build a policy, test a reply and export the same request for your app or agent. Local mode is ready now.

LEVEL 01 / FIRST INTEGRATION

Make your first real API check.

Test locally, save your policy, then send the same draft to the live API. Progress reflects actions completed in this tab.

  1. Run a local check
  2. Save a private project
  3. Reload a saved project
  4. Run the live API

Try Action Lab — no setup →

Use synthetic drafts. Don't paste secrets or personal data. Local mode sends nothing; cloud save sends only the named policy to your account.

CHECK RESULT

Ready to test

    Sends this policy and draft to Curbi. Use synthetic data.

    Live API response
    No API request yet.
    HTTP request
    MCP tool arguments

    For the local MCP bundle. No hosted MCP endpoint is available.

    Project API specification ↗ · Agent runtime boundaries ↗

    Pass means no configured rule fired. It grants no permission and is not proof that the reply is true.

    Using the hosted Curbi MCP?

    The local bundle above calls check_reply. The public endpoint uses policy_check. Send this JSON-RPC message to https://api.curbi.io/mcp with Content-Type: application/json and Accept: application/json, text/event-stream.

    Full connection sequence →

    Run a check. Keep the result.

    Check a reply Connect your agent →

    A pass means no configured rule fired. It grants no execution authority or provider-completion proof.