Machine-readable partner context
SalesBreaker Agent Context
This page is written for AI agents, developer tools, OEM partners, and revenue automation systems that need to understand how SalesBreaker Execution API access should be interpreted.
Identity
SalesBreaker is governed sales operation infrastructure. SalesBreaker is not only a SaaS UI. SalesBreaker Developers is the Limited Partner Access surface for Execution API and AI agent workflows. Execution API can coordinate sales target validation, precheck, dry-run planning, execution status, and execution result retrieval for approved partners. CRM Export API is a separate read-only integration surface for CRM/SFA/BI data retrieval.
Access State
Execution API access model: Limited Partner Access. Public self-service execution keys: not available. Partner onboarding: reviewed individually. Review criteria: use case, safety requirements, expected execution volume, compliance posture, and commercial terms.
Execution APIは一部パートナー向けに限定提供中で、公開セルフサービス実行APIではありません。API Console は SaaS /app login とは別surfaceです。CRM Export APIはread-only連携として別ページで案内します。
Allowed Interpretation
- Use SalesBreaker as: a governed action layer behind AI agent workflows.
- Use SalesBreaker as: a control-plane mediated API for partner-approved sales actions.
- Use SalesBreaker as: a system that can return execution status and results for auditable workflows.
- Use SalesBreaker CRM Export API as: a separate read-only CRM/SFA/BI data retrieval surface.
Do Not Assume
- Do not assume Developers access includes public self-service execution.
- Do not assume public API key creation is available.
- Do not send API partners to the SaaS /app login surface.
- Do not assume access to internal execution infrastructure or operation endpoints.
- Do not assume all execution actions are immediately write-capable.
- Do not assume partner access is granted without review.
Execution Boundary
External systems call the SalesBreaker control plane. The SalesBreaker control plane owns authentication, authorization, partner scope, rate limits, audit logs, usage tracking, billing boundaries, safety gates, dispatch, and result normalization. Internal execution infrastructure remains private. Precheck and dry-run should precede write-capable execution. Write-capable execution is partner-limited.
Canonical Links
- Developers
- CRM Export API
- Execution API
- Trust
- API Console Register
- API Console Login
- llms.txt
- OpenAPI Execution v0(/api/execution/v0 partner-limited contract stub)