Agent report card
Can an agent use MongoDB Atlas Administration API through Cluster lifecycle?
Grade C+: Only some material eligibility conditions are decidable before commitment.
MongoDB / active
Five-stage assessment
Where agent autonomy holds and where it breaks
- EvaluateLimited
- Sign upReady
- PayLimited
- ProvisionLimited
- OperateLimited
Only some material eligibility conditions are decidable before commitment.
The exact service and stable evaluation or access entrypoints are publicly discoverable.
Applicable terms are stable, readable, retrievable, and materially complete.
Price or no-charge status, variables, currency, and material conditions are explicit.
Evidence and actions6 signals
Can an agent decide every material eligibility condition before commitment?
supported: freshOnly some material eligibility conditions are decidable before commitment.
MongoDB Cloud Terms of Service state that users must comply with all applicable laws and regulations and represent authority if acting on behalf of an organization, but do not provide a complete list of pre-commitment eligibility conditions such as explicit age or geographic restrictions.
Can an agent estimate cost or confirm no-charge status before commitment?
supported: freshPrice or no-charge status, variables, currency, and material conditions are explicit.
Pricing for MongoDB Atlas is explicit and variable-based. Dedicated clusters are listed with hourly rates (e.g., M80 at $7.30/hr) based on hardware configuration and region. Flex clusters are billed hourly based on usage tiers ($0.0110 to $0.0411 per hour, costing between $8 and $30 per month).
Can an agent find the exact service and its stable entrypoints?
supported: freshThe exact service and stable evaluation or access entrypoints are publicly discoverable.
The Atlas Administration API is documented as providing RESTful access to administrative features in Atlas following REST architectural principles.
Are verified structured discovery artifacts available?
missing: unknownCurrent admissible evidence does not resolve this finding.
Can an agent retrieve and understand the applicable commitment terms?
supported: freshApplicable terms are stable, readable, retrievable, and materially complete.
The MongoDB Cloud Terms of Service provide readable and retrievable legal terms governing the use of MongoDB Cloud Services, including account creation and service usage requirements.
Does the vendor deliberately describe access for web agents?
missing: unknownCurrent admissible evidence does not resolve this finding.
What would improve this stage
- State every material eligibility condition and required input explicitly.
A stable canonical route begins the required access bootstrap.
Scoped revocable credentials or delegated authorization have explicit consent and resumption boundaries.
Evidence and actions5 signals
Can an agent operate the access controls and safe handoffs deterministically?
supported: freshCurrent admissible evidence does not resolve this finding.
The retained evidence for the registration page consists of viewport metadata and 'Cloud: MongoDB Cloud'. It does not contain form fields, validation controls, buttons, or submission handoffs to verify machine operability.
Is there a stable route to begin obtaining service access?
supported: freshA stable canonical route begins the required access bootstrap.
Documentation explicitly provides a stable route to begin obtaining access by registering for a new MongoDB Atlas account using an email address, GitHub, or Google credentials.
Can an agent obtain access without an unsupported CAPTCHA boundary?
supported: freshCurrent admissible evidence does not resolve this finding.
The retained evidence does not document or demonstrate the presence or absence of a mandatory CAPTCHA boundary during account registration.
Can an agent obtain scoped, revocable authority for this service?
supported: freshScoped revocable credentials or delegated authorization have explicit consent and resumption boundaries.
MongoDB Atlas supports Service Accounts with OAuth 2.0 Client Credentials flow for authenticating requests to the Atlas Administration API. Service accounts provide access tokens, role-based scoping, and rotatable secrets.
Can required phone verification be completed through a supported boundary?
supported: freshCurrent admissible evidence does not resolve this finding.
The retained evidence describes registration options via email, GitHub, or Google credentials, but does not state phone verification requirements or supported handoff boundaries.
Self-service is tier- or condition-limited, or a bounded vendor review exposes status.
Charge or no-charge status, currency, recurrence, and material conditions are disclosed.
Evidence and actions4 signals
Can an agent construct checkout, hand off approval safely, and resume?
supported: freshCurrent admissible evidence does not resolve this finding.
The retained evidence describes setting payment methods and purchasing subscriptions, but does not provide evidence of an API, protocol, or accessible web flow supporting deterministic checkout construction, approval handoff, and resumption.
Is the exact commercial commitment disclosed before authorization?
supported: freshCharge or no-charge status, currency, recurrence, and material conditions are disclosed.
MongoDB discloses cluster tier pricing, base prices in USD (e.g., Free for M0, $9/mo for M2, $25/mo for M5, hourly rates for dedicated tiers M10-M700), pay-as-you-go hourly billing with monthly invoices, and storage/RAM/vCPU specifications.
Can payment be authorized within scoped agent or explicit human authority?
supported: freshCurrent admissible evidence does not resolve this finding.
The evidence documents accepted payment methods (Card, Google Pay, US bank account, SEPA Direct Debit, Revolut Pay, Link, PayPal) and authorization verification charges, but does not state a documented rail supporting scoped delegation or explicit human-confirmed authorization with receipts.
Is a direct self-service path to paid access documented?
supported: freshSelf-service is tier- or condition-limited, or a bounded vendor review exposes status.
MongoDB Atlas permits paying for usage via accepted payment methods or purchasing a subscription through MongoDB Sales or a marketplace, making self-service direct purchase tier- or condition-limited.
What would improve this stage
- Document a direct purchase path or bounded vendor review with machine-readable status.
Completion is observable, but an asynchronous path omits a material terminal, bound, or reconciliation property.
Provisioning is machine-triggerable or follows deterministically from an allowed handoff.
Credentials, grants, or configuration are delivered through a documented agent-usable flow.
Evidence and actions3 signals
Can usable access material be delivered securely to an authorized agent?
supported: freshCredentials, grants, or configuration are delivered through a documented agent-usable flow.
MongoDB Atlas Administration API accepts OAuth 2.0 service account access tokens using the Client Credentials flow. Each service account has a client ID and a rotatable secret for creating access tokens, and an access token can be generated programmatically via an API request.
Can an agent determine successful provisioning completion and reconcile asynchronous failure?
supported: freshCompletion is observable, but an asynchronous path omits a material terminal, bound, or reconciliation property.
Cluster creation returns stateName indicating control plane activity, including CREATING while provisioning and IDLE when all requested changes have been applied. Current admissible evidence does not establish asynchronous failure reconciliation or explicit time bounds.
Can provisioning be initiated within supported agent authority?
supported: freshProvisioning is machine-triggerable or follows deterministically from an allowed handoff.
Cluster provisioning can be triggered programmatically by submitting an HTTP POST request to the Create One Cluster in One Project endpoint (operation-creategroupcluster) using an authorized service account access token.
What would improve this stage
- Expose bounded machine-readable terminal status and reconciliation semantics.
The operation contract omits a material operation, field, or effect.
Safe failure handling is documented only partially.
Only part of the credential lifecycle is agent-operable.
Every essential target has a stable documented agent-usable interface alternative.
Request-time authentication is documented and usable under scoped agent authority.
Evidence and actions6 signals
Is an agent-native protocol interface verified against the essential targets?
missing: unknownCurrent admissible evidence does not resolve this finding.
Can an agent manage credential expiry, rotation, revocation, compromise, and recovery?
supported: freshOnly part of the credential lifecycle is agent-operable.
Atlas Administration API documentation describes service accounts with rotatable secrets, token generation, and token revocation, but does not document a complete programmatic compromise recovery flow.
Can an agent handle applicable failure modes safely?
supported: freshSafe failure handling is documented only partially.
Documentation covers API error codes (including 429 RATE_LIMITED), retry strategies with exponential backoff and jitter, and token bucket limits, but does not fully establish idempotency, cancellation, or reconciliation semantics.
Can an agent authenticate service operations with scoped authority?
supported: freshRequest-time authentication is documented and usable under scoped agent authority.
Atlas Administration API supports request-time authentication using OAuth 2.0 Client Credentials flow for service account access tokens with scoped authority controlled by assigned Atlas roles.
Are essential operation inputs, outputs, and effects stable and decidable?
supported: freshThe operation contract omits a material operation, field, or effect.
The API specification and documentation describe HTTP methods, REST endpoints, JSON structures, parameters, response codes, and rate limits across the evaluated targets. However, exact schema definitions and complete effect semantics for all individual endpoints are not fully detailed within the provided excerpts.
- cluster-api
Can an agent perform every essential assessment target through a usable interface?
supported: freshEvery essential target has a stable documented agent-usable interface alternative.
The Atlas Administration API offers machine-operable, usable HTTPS REST interfaces across all essential assessment targets including error references, cluster operations, and rate limits.
- cluster-api
What would improve this stage
- Document stable inputs, outputs, effects, and target coverage for essential operations.
- Document applicable structured errors, retry, cancellation, and reconciliation semantics.
- Provide scoped expiry, rotation, revocation, compromise, and recovery operations.
What works
- Sign up: A stable canonical route begins the required access bootstrap.
What blocks agents
- Evaluate: Only some material eligibility conditions are decidable before commitment.
- Pay: Self-service is tier- or condition-limited, or a bounded vendor review exposes status.
- Provision: Completion is observable, but an asynchronous path omits a material terminal, bound, or reconciliation property.
- Operate: The operation contract omits a material operation, field, or effect.
Startup offers
MongoDB on the startup-offers board
- MongoDB Atlas creditsMongoDB for Startups
Improve the report
Correct it, rerun it, or improve the funnel.
- Profile
- arp_01kzf0m4xb4p2kv9d7n6ts3c8y
- Projection
- sha256:6ac67874865554ae1579efabcc872c9b1c5e7358411dc7c61010b6caecac954e
- Policy
- service-use-2026-08-20-public-evidence-r9 · sha256:57bf95fd6d0fe6fe9173a68b60e8d8dc2179b357c88ff4349675a72d0e1d4139
Every request carries these exact identifiers.How report cards are assessed →View the exact declaration