Provenance
observed · 8 Aug
Freshness
fresh
Dispute
none
Revision
sha256:c2ad3b65e864…

Agent report card

Can an agent use HubSpot CRM API through API integration lifecycle?

Grade D: Eligibility depends on information or judgment unavailable to an agent.

HubSpot / active

Agent ReadinessDBlocked
Coverage
complete: 11/11
Freshness
fresh
Last tested
Evidence
observed: not disputed

Five-stage assessment

Where agent autonomy holds and where it breaks

First break: Evaluate

  1. Evaluate

    Blocked

    Eligibility depends on information or judgment unavailable to an agent.

    Only part of the applicable terms is machine-readable.

    An ARD declaration has not been established.

    An agent can discover the product and funnel from the tested public entrypoints.

    Pricing or the absence of a charge is explicit and machine-readable.

    Evidence and actions

    ARD declaration unknown

    missing: unknown

    An ARD declaration has not been established.

    ard_declaration: Unknown

    Decidable eligibility unavailable

    supported: fresh

    Eligibility depends on information or judgment unavailable to an agent.

    Public eligibility criteria for the HubSpot API integration platform depend on user-specific agreement choices and partner/customer classifications that cannot be fully decided by an automated agent alone.

    decidable_eligibility: Blocked: tested 7 Aug

    Method http 1

    Machine discovery

    supported: fresh

    An agent can discover the product and funnel from the tested public entrypoints.

    HubSpot's developer documentation index and API reference entrypoints provide machine-discoverable documentation and structure (including llms.txt and structured metadata).

    machine_discovery: Ready: tested 7 Aug

    Method http 1

    Readable pricing

    supported: fresh

    Pricing or the absence of a charge is explicit and machine-readable.

    HubSpot explicitly documents that developer accounts and API access for building and testing integrations are free without requiring a paid subscription.

    readable_pricing: Ready: tested 8 Aug

    Method http 1

    Structured terms limited

    supported: fresh

    Only part of the applicable terms is machine-readable.

    HubSpot legal terms are accessible via stable, readable web pages across customer, developer, and public categories, but are not provided as a structured data API/contract.

    structured_terms: Limited: tested 7 Aug

    Method http 1

    What blocks agents

    • Eligibility depends on information or judgment unavailable to an agent.

    What would improve this stage

    • Publish complete, explicit eligibility criteria and required inputs.
    • Publish complete applicable terms in a stable machine-readable document.

  2. Sign up

    Ready

    A stable signup entrypoint is available.

    Machine-operable signup has not been established.

    Whether CAPTCHA blocks signup has not been established.

    Whether phone verification is required has not been established.

    A scoped, revocable machine identity flow is documented, including explicit human authorization boundaries.

    Evidence and actions

    CAPTCHA-free signup unknown

    supported: fresh

    Whether CAPTCHA blocks signup has not been established.

    Reid/headless capture confirms landing on signup page but does not conclusively establish whether CAPTCHA is absent across the complete signup flow.

    captcha_free: Unknown: tested 7 Aug

    Method headless 1

    Machine-operable signup unknown

    supported: fresh

    Machine-operable signup has not been established.

    The signup landing page content was captured, but machine-operability of the complete signup form fields could not be verified from the initial page payload alone.

    machine_operable_form: Unknown: tested 7 Aug

    Method headless 1

    Phone-free signup unknown

    supported: fresh

    Whether phone verification is required has not been established.

    Whether phone or SMS verification is required during the signup flow is not established in the provided signup evidence.

    phone_verification_free: Unknown: tested 7 Aug

    Method headless 1

    Stable signup entrypoint

    supported: fresh

    A stable signup entrypoint is available.

    A stable HTTP signup entrypoint was accessible at https://app.hubspot.com/signup-hubspot/crm.

    stable_entrypoint: Ready: tested 7 Aug

    Method http 1

    Supported identity flow

    supported: fresh

    A scoped, revocable machine identity flow is documented, including explicit human authorization boundaries.

    HubSpot documents a scoped, revocable OAuth identity flow featuring explicit human authorization boundaries and token refresh mechanisms.

    supported_identity_flow: Ready: tested 7 Aug

    Method headless 1

  3. Pay

    Not applicable

    Evidence establishes that this funnel has no payment step.

    Evidence establishes that this funnel has no checkout step.

    Evidence establishes that this funnel has no payment step.

    Evidence establishes that this funnel has no purchase step.

    Evidence and actions

    Explicit price not applicable

    supported: fresh

    Evidence establishes that this funnel has no payment step.

    Evidence confirms that developers can build apps and access public APIs using a free HubSpot account without requiring a paid subscription or payment step.

    explicit_price: Not applicable: tested 8 Aug

    Method http 1

    Machine-operable checkout not applicable

    supported: fresh

    Evidence establishes that this funnel has no checkout step.

    No checkout or payment step is required as developer platform features and accounts are free.

    machine_operable_checkout: Not applicable: tested 7 Aug

    Method headless 1

    Sales-free purchase not applicable

    supported: fresh

    Evidence establishes that this funnel has no purchase step.

    No payment or purchase step exists for developer access, making sales intervention not applicable.

    sales_intervention_free: Not applicable: tested 7 Aug

    Method headless 1

    Supported payment rail not applicable

    supported: fresh

    Evidence establishes that this funnel has no payment step.

    Payment rails are not applicable because developer accounts and API testing do not require payment.

    supported_payment_rail: Not applicable: tested 7 Aug

    Method headless 1

  4. Provision

    Limited

    Only part of the provisioning lifecycle exposes machine-readable status.

    Automatic activation has not been established.

    A bounded provisioning delay has not been established.

    Usable credentials or delegated access are delivered through a documented flow.

    Evidence and actions

    Automatic activation unknown

    supported: fresh

    Automatic activation has not been established.

    Retained evidence for the headless capture of crm-operations returned a 500 error page, which does not establish whether automatic activation is present.

    automatic_activation: Unknown: tested 7 Aug

    Method headless 1

    Bounded provisioning delay unknown

    supported: fresh

    A bounded provisioning delay has not been established.

    Documentation describes batch operations and API usage limits, but does not state a documented bounded delay for record or service provisioning completion.

    bounded_delay: Unknown: tested 7 Aug

    Method http 1

    Credential delivery

    supported: fresh

    Usable credentials or delegated access are delivered through a documented flow.

    HubSpot documents an OAuth authorization flow where exchanging the authorization code with /oauth/v3/token delivers an access token and refresh token.

    credential_delivery: Ready: tested 7 Aug

    Method headless 1

    Machine-readable provisioning status limited

    supported: fresh

    Only part of the provisioning lifecycle exposes machine-readable status.

    Batch create operations allow enabling multi-status error responses with a trace ID and terminal status, but complete asynchronous provisioning lifecycle tracking is not fully exposed across all operations.

    machine_readable_status: Limited: tested 7 Aug

    Method http 1

    What would improve this stage

    • Expose deterministic provisioning progress, terminal states, errors, cancellation, and reconciliation where applicable.

  5. Operate

    Ready

    A documented API or tool interface is available for operation.

    An agent protocol interface has not been established.

    Authentication is documented and usable within an agent authorization boundary.

    Limits, structured errors, retry behavior, and idempotency semantics are documented where applicable.

    Credential rotation, revocation, retry, and recovery paths are documented within delegated authority.

    Evidence and actions

    Agent protocol interface unknown

    missing: unknown

    An agent protocol interface has not been established.

    agent_protocol_interface: Unknown

    API or tool access

    supported: fresh

    A documented API or tool interface is available for operation.

    HubSpot provides documented CRM API endpoints under api.hubapi.com for managing records such as contacts and deals.

    api_tool_access: Ready: tested 7 Aug

    Method http 1

    Delegated recovery

    supported: fresh

    Credential rotation, revocation, retry, and recovery paths are documented within delegated authority.

    HubSpot documents token generation, access token refresh, and retry behavior for rate limits and transient errors.

    delegated_recovery: Ready: tested 7 Aug

    Method http 1

    Documented limits and errors

    supported: fresh

    Limits, structured errors, retry behavior, and idempotency semantics are documented where applicable.

    HubSpot documents batch request limits (100 inputs), detailed error structures, and retry/rate-limiting guidelines.

    documented_limits_errors: Ready: tested 7 Aug

    Method http 1

    Usable authentication

    supported: fresh

    Authentication is documented and usable within an agent authorization boundary.

    HubSpot documents OAuth authentication using authorization codes to obtain access tokens for API requests.

    usable_authentication: Ready: tested 7 Aug

    Method http 1

What works

  • Sign up: A stable signup entrypoint is available.
  • Pay: Evidence establishes that this funnel has no payment step.
  • Operate: A documented API or tool interface is available for operation.

What blocks agents

  • Evaluate: Eligibility depends on information or judgment unavailable to an agent.
  • Provision: Only part of the provisioning lifecycle exposes machine-readable status.

Improve the report

Correct it, rerun it, or improve the funnel

Every request carries the exact profile revision, projection, declaration, and Catalog release.

Report outdated evidenceRequest reassessmentClaim this vendorView the exact declaration
Method, policy, and immutable identifiers

Complete, fresh evidence for the core service lifecycle first applies hard stage severity, then grades the share of applicable evidenced signals that are constrained. Optional blocker probes affect the grade when established and remain visible as unknown when public evidence cannot establish them.

Any incomplete, contradictory, unsupported, or non-fresh required evidence produces an unrated profile. A failed Evaluate, Sign up, or Pay stage derives D; a failed Provision or Operate stage derives F; otherwise constrained-signal ratio derives A+ through C.

Profile ID
arp_01kzf0m4xa1m8yr7cf5q2b9vn6
Revision
sha256:c2ad3b65e86423943af0819b8bd2554895af553186b5407b556dea1f8562d75a
Projection
sha256:00947fefc2eebdcf69226735ae062d95b830ad4cdc41d82b1cfca5c21a628a2c
Policy
service-lifecycle-2026-08-08-calibrated: sha256:334e56852b5c38e178fcea839cfba680fb82dd96693842d933776baed21d63df
Base Catalog release
sha256:5082ec07047a2324648f569d234cc64342ce2707b2f3d77fde8fc06af517cee6