Agent report cards

Can an agent use the service?

sourcey assesses the service lifecycle: evaluate, establish access, pay when required, provision, and operate. Each grade is grounded in service-use evidence while keeping human account and billing prerequisites visible.

What the grade means

One visible answer, five evidence-backed stages

Ready, limited, blocked, unknown, and not applicable are policy projections over exact signal observations. The grade is derived deterministically; it is not written by a model or vendor.

  1. EvaluateCan an agent discover and understand the product?
  2. Sign upCan it establish authorized access, and where is human verification required?
  3. PayCan it understand and complete the commercial step?
  4. ProvisionCan it activate access and know when it is ready?
  5. OperateCan it authenticate, use, recover, and understand limits?

Published report cards

23 shown
  • Microsoft Azure

    API resource managementtested

    Safe failure handling is documented only partially.

    1. Evaluate: Ready. The exact service and stable evaluation or access entrypoints are publicly discoverable.
    2. Sign up: Ready. A stable canonical route begins the required access bootstrap.
    3. Pay: Ready. Charge or no-charge status, currency, recurrence, and material conditions are disclosed.
    4. Provision: Ready. Provisioning is machine-triggerable or follows deterministically from an allowed handoff.
    5. Operate: Limited. Safe failure handling is documented only partially.
    A
  • AWS Cloud

    API resource managementtested

    Completion is observable, but an asynchronous path omits a material terminal, bound, or reconciliation property.

    1. Evaluate: Ready. The exact service and stable evaluation or access entrypoints are publicly discoverable.
    2. Sign up: Ready. A stable canonical route begins the required access bootstrap.
    3. Pay: Ready. Charge or no-charge status, currency, recurrence, and material conditions are disclosed.
    4. Provision: Limited. Completion is observable, but an asynchronous path omits a material terminal, bound, or reconciliation property.
    5. Operate: Limited. Safe failure handling is documented only partially.
    B+
  • Google Cloud

    API resource managementtested

    Completion is observable, but an asynchronous path omits a material terminal, bound, or reconciliation property.

    1. Evaluate: Ready. The exact service and stable evaluation or access entrypoints are publicly discoverable.
    2. Sign up: Ready. A stable canonical route begins the required access bootstrap.
    3. Pay: Ready. Charge or no-charge status, currency, recurrence, and material conditions are disclosed.
    4. Provision: Limited. Completion is observable, but an asynchronous path omits a material terminal, bound, or reconciliation property.
    5. Operate: Limited. Safe failure handling is documented only partially.
    B+
  • Anthropic API

    API service lifecycletested

    Machine credentials exist but require manual copying, broad authority, or weak lifecycle support.

    1. Evaluate: Ready. The exact service and stable evaluation or access entrypoints are publicly discoverable.
    2. Sign up: Limited. Machine credentials exist but require manual copying, broad authority, or weak lifecycle support.
    3. Pay: Ready. Charge or no-charge status, currency, recurrence, and material conditions are disclosed.
    4. Provision: Limited. Delivery needs additional human transfer or has weak scope or lifecycle semantics.
    5. Operate: Limited. Safe failure handling is documented only partially.
    B
  • Cloudflare Developer Platform

    API resource managementtested

    Machine credentials exist but require manual copying, broad authority, or weak lifecycle support.

    1. Evaluate: Ready. The exact service and stable evaluation or access entrypoints are publicly discoverable.
    2. Sign up: Limited. Machine credentials exist but require manual copying, broad authority, or weak lifecycle support.
    3. Pay: Limited. Self-service is tier- or condition-limited, or a bounded vendor review exposes status.
    4. Provision: Limited. Delivery needs additional human transfer or has weak scope or lifecycle semantics.
    5. Operate: Limited. Safe failure handling is documented only partially.
    C+
  • Datadog API

    Monitor operationstested

    Machine credentials exist but require manual copying, broad authority, or weak lifecycle support.

    1. Evaluate: Ready. The exact service and stable evaluation or access entrypoints are publicly discoverable.
    2. Sign up: Limited. Machine credentials exist but require manual copying, broad authority, or weak lifecycle support.
    3. Pay: Limited. The public commitment omits a material component until later in the flow.
    4. Provision: Limited. Delivery needs additional human transfer or has weak scope or lifecycle semantics.
    5. Operate: Limited. Safe failure handling is documented only partially.
    C+
  • DigitalOcean Cloud

    API resource managementtested

    Machine credentials exist but require manual copying, broad authority, or weak lifecycle support.

    1. Evaluate: Ready. The exact service and stable evaluation or access entrypoints are publicly discoverable.
    2. Sign up: Limited. Machine credentials exist but require manual copying, broad authority, or weak lifecycle support.
    3. Pay: Ready. Charge or no-charge status, currency, recurrence, and material conditions are disclosed.
    4. Provision: Limited. Delivery needs additional human transfer or has weak scope or lifecycle semantics.
    5. Operate: Limited. Safe failure handling is documented only partially.
    B
  • GitHub REST API

    Repository operationstested

    Delivery needs additional human transfer or has weak scope or lifecycle semantics.

    1. Evaluate: Ready. The exact service and stable evaluation or access entrypoints are publicly discoverable.
    2. Sign up: Ready. A stable canonical route begins the required access bootstrap.
    3. Pay: Ready. Charge or no-charge status, currency, recurrence, and material conditions are disclosed.
    4. Provision: Limited. Delivery needs additional human transfer or has weak scope or lifecycle semantics.
    5. Operate: Limited. Safe failure handling is documented only partially.
    B+
  • HubSpot CRM API

    API integration lifecycletested

    The public commitment omits a material component until later in the flow.

    1. Evaluate: Ready. The exact service and stable evaluation or access entrypoints are publicly discoverable.
    2. Sign up: Ready. A stable canonical route begins the required access bootstrap.
    3. Pay: Limited. The public commitment omits a material component until later in the flow.
    4. Provision: Limited. Delivery needs additional human transfer or has weak scope or lifecycle semantics.
    5. Operate: Limited. Safe failure handling is documented only partially.
    B
  • MongoDB Atlas Administration API

    Cluster lifecycletested

    Machine credentials exist but require manual copying, broad authority, or weak lifecycle support.

    1. Evaluate: Ready. The exact service and stable evaluation or access entrypoints are publicly discoverable.
    2. Sign up: Limited. Machine credentials exist but require manual copying, broad authority, or weak lifecycle support.
    3. Pay: Limited. The public commitment omits a material component until later in the flow.
    4. Provision: Limited. Completion is observable, but an asynchronous path omits a material terminal, bound, or reconciliation property.
    5. Operate: Limited. Safe failure handling is documented only partially.
    C+
  • Neon API

    Project and database lifecycletested

    Discovery works but is incomplete, context-dependent, split, or unstable.

    1. Evaluate: Limited. Discovery works but is incomplete, context-dependent, split, or unstable.
    2. Sign up: Limited. Machine credentials exist but require manual copying, broad authority, or weak lifecycle support.
    3. Pay: Ready. Charge or no-charge status, currency, recurrence, and material conditions are disclosed.
    4. Provision: Limited. Delivery needs additional human transfer or has weak scope or lifecycle semantics.
    5. Operate: Limited. Safe failure handling is documented only partially.
    C+
  • Notion API

    API integration lifecycletested

    Delivery needs additional human transfer or has weak scope or lifecycle semantics.

    1. Evaluate: Ready. The exact service and stable evaluation or access entrypoints are publicly discoverable.
    2. Sign up: Ready. A stable canonical route begins the required access bootstrap.
    3. Pay: Ready. Charge or no-charge status, currency, recurrence, and material conditions are disclosed.
    4. Provision: Limited. Delivery needs additional human transfer or has weak scope or lifecycle semantics.
    5. Operate: Limited. Safe failure handling is documented only partially.
    B+
  • OpenAI API

    API service lifecycletested

    Machine credentials exist but require manual copying, broad authority, or weak lifecycle support.

    1. Evaluate: Ready. The exact service and stable evaluation or access entrypoints are publicly discoverable.
    2. Sign up: Limited. Machine credentials exist but require manual copying, broad authority, or weak lifecycle support.
    3. Pay: Ready. Charge or no-charge status, currency, recurrence, and material conditions are disclosed.
    4. Provision: Limited. Delivery needs additional human transfer or has weak scope or lifecycle semantics.
    5. Operate: Limited. Safe failure handling is documented only partially.
    B
  • Pinecone Database API

    Index lifecycletested

    Machine credentials exist but require manual copying, broad authority, or weak lifecycle support.

    1. Evaluate: Ready. The exact service and stable evaluation or access entrypoints are publicly discoverable.
    2. Sign up: Limited. Machine credentials exist but require manual copying, broad authority, or weak lifecycle support.
    3. Pay: Ready. Charge or no-charge status, currency, recurrence, and material conditions are disclosed.
    4. Provision: Limited. Delivery needs additional human transfer or has weak scope or lifecycle semantics.
    5. Operate: Limited. Safe failure handling is documented only partially.
    B
  • Resend Email API

    Email operationstested

    Machine credentials exist but require manual copying, broad authority, or weak lifecycle support.

    1. Evaluate: Ready. The exact service and stable evaluation or access entrypoints are publicly discoverable.
    2. Sign up: Limited. Machine credentials exist but require manual copying, broad authority, or weak lifecycle support.
    3. Pay: Limited. Self-service is tier- or condition-limited, or a bounded vendor review exposes status.
    4. Provision: Ready. Provisioning is machine-triggerable or follows deterministically from an allowed handoff.
    5. Operate: Limited. Only part of the credential lifecycle is agent-operable.
    B
  • Sentry Web API

    Issue and project operationstested

    A mandatory CAPTCHA has no supported agent-safe route.

    1. Evaluate: Ready. The exact service and stable evaluation or access entrypoints are publicly discoverable.
    2. Sign up: Blocked. A mandatory CAPTCHA has no supported agent-safe route.
    3. Pay: Limited. The public commitment omits a material component until later in the flow.
    4. Provision: Ready. Provisioning is machine-triggerable or follows deterministically from an allowed handoff.
    5. Operate: Limited. Safe failure handling is documented only partially.
    D
  • Slack Web API

    Workspace app operationstested

    Self-service is tier- or condition-limited, or a bounded vendor review exposes status.

    1. Evaluate: Ready. The exact service and stable evaluation or access entrypoints are publicly discoverable.
    2. Sign up: Ready. A stable canonical route begins the required access bootstrap.
    3. Pay: Limited. Self-service is tier- or condition-limited, or a bounded vendor review exposes status.
    4. Provision: Ready. Provisioning is machine-triggerable or follows deterministically from an allowed handoff.
    5. Operate: Limited. Safe failure handling is documented only partially.
    B+
  • Stripe Payments API

    API payment lifecycletested

    Machine credentials exist but require manual copying, broad authority, or weak lifecycle support.

    1. Evaluate: Ready. The exact service and stable evaluation or access entrypoints are publicly discoverable.
    2. Sign up: Limited. Machine credentials exist but require manual copying, broad authority, or weak lifecycle support.
    3. Pay: Limited. Self-service is tier- or condition-limited, or a bounded vendor review exposes status.
    4. Provision: Limited. Delivery needs additional human transfer or has weak scope or lifecycle semantics.
    5. Operate: Limited. Only part of the credential lifecycle is agent-operable.
    C+
  • Twilio Messaging API

    Message operationstested

    Machine credentials exist but require manual copying, broad authority, or weak lifecycle support.

    1. Evaluate: Ready. The exact service and stable evaluation or access entrypoints are publicly discoverable.
    2. Sign up: Limited. Machine credentials exist but require manual copying, broad authority, or weak lifecycle support.
    3. Pay: Ready. Charge or no-charge status, currency, recurrence, and material conditions are disclosed.
    4. Provision: Limited. Completion is observable, but an asynchronous path omits a material terminal, bound, or reconciliation property.
    5. Operate: Limited. Safe failure handling is documented only partially.
    B
  • Vercel REST API

    Deployment operationstested

    Machine credentials exist but require manual copying, broad authority, or weak lifecycle support.

    1. Evaluate: Ready. The exact service and stable evaluation or access entrypoints are publicly discoverable.
    2. Sign up: Limited. Machine credentials exist but require manual copying, broad authority, or weak lifecycle support.
    3. Pay: Ready. Charge or no-charge status, currency, recurrence, and material conditions are disclosed.
    4. Provision: Limited. Completion is observable, but an asynchronous path omits a material terminal, bound, or reconciliation property.
    5. Operate: Limited. Safe failure handling is documented only partially.
    B
  • Cloudflare 1.1.1.1 Public DNS

    DNS over HTTPS querytested

    The exact service and stable evaluation or access entrypoints are publicly discoverable.

    1. Evaluate: Ready. The exact service and stable evaluation or access entrypoints are publicly discoverable.
    2. Sign up: Not applicable. Admitted evidence establishes that this step does not apply to the assessed service.
    3. Pay: Ready. Charge or no-charge status, currency, recurrence, and material conditions are disclosed.
    4. Provision: Not applicable. Admitted evidence establishes that this step does not apply to the assessed service.
    5. Operate: Ready. Every essential target has a stable documented agent-usable interface alternative.
    A+
  • GitHub Enterprise Server 3.21

    Repository operationstested

    Paid access requires opaque or unbounded sales intervention.

    1. Evaluate: Ready. The exact service and stable evaluation or access entrypoints are publicly discoverable.
    2. Sign up: Limited. Only part of the access flow is operable or a bounded human step remains.
    3. Pay: Blocked. Paid access requires opaque or unbounded sales intervention.
    4. Provision: Limited. Delivery needs additional human transfer or has weak scope or lifecycle semantics.
    5. Operate: Limited. Safe failure handling is documented only partially.
    D
  • OpenRouter API

    Model access lifecycletested

    Safe failure handling is documented only partially.

    1. Evaluate: Ready. The exact service and stable evaluation or access entrypoints are publicly discoverable.
    2. Sign up: Ready. A stable canonical route begins the required access bootstrap.
    3. Pay: Ready. Charge or no-charge status, currency, recurrence, and material conditions are disclosed.
    4. Provision: Ready. Provisioning is machine-triggerable or follows deterministically from an allowed handoff.
    5. Operate: Limited. Safe failure handling is documented only partially.
    A