Agent report card
Can an agent use MongoDB Atlas Administration API through Cluster lifecycle?
Grade B: Only part of the applicable terms is machine-readable.
MongoDB / active
Five-stage assessment
Where agent autonomy holds and where it breaks
First break: Evaluate
Evaluate
LimitedOnly part of the applicable terms is machine-readable.
Eligibility is only partly decidable from public criteria.
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: unknownAn ARD declaration has not been established.
Decidable eligibility limited
supported: freshEligibility is only partly decidable from public criteria.
MongoDB Terms of Use set public legal criteria and usage constraints (e.g. registration accuracy, export control, rules of conduct), but final eligibility or termination remains subject to MongoDB's discretionary judgment and rights.
Machine discovery
supported: freshAn agent can discover the product and funnel from the tested public entrypoints.
MongoDB Atlas Administration API reference documentation is publicly discoverable and provides machine-readable specifications, endpoints, and developer guidance.
Readable pricing
supported: freshPricing or the absence of a charge is explicit and machine-readable.
MongoDB publishes explicit, machine-readable pricing tiers for Atlas, including M0 Free, Flex, and Dedicated cluster hourly rates and storage options.
Structured terms limited
supported: freshOnly part of the applicable terms is machine-readable.
The Terms of Use are made available as readable HTML text on the website, but are not provided as a structured machine-readable contract (e.g., JSON schema).
What would improve this stage
- Publish complete applicable terms in a stable machine-readable document.
- Publish complete, explicit eligibility criteria and required inputs.
Sign up
ReadyA 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: freshWhether CAPTCHA blocks signup has not been established.
The retained evidence for the signup flow contains minimal page content and does not confirm whether a CAPTCHA is present or absent.
Machine-operable signup unknown
supported: freshMachine-operable signup has not been established.
The retained snippet from the signup page does not provide evidence of machine-operable form controls.
Phone-free signup unknown
supported: freshWhether phone verification is required has not been established.
The available signup evidence is insufficient to establish whether phone or SMS verification is required.
Stable signup entrypoint
supported: freshA stable signup entrypoint is available.
The account registration endpoint responds at a stable registration URL with basic page structure.
Supported identity flow
supported: freshA scoped, revocable machine identity flow is documented, including explicit human authorization boundaries.
Atlas Administration API documentation defines identity authentication methods including Service Accounts with OAuth 2.0 and API Keys with HTTP Digest Authentication.
Pay
ReadyThe required price or no-charge status is explicit before commitment.
Machine-operable checkout has not been established.
A supported payment rail has not been established.
Whether sales intervention is required has not been established.
Evidence and actions
Explicit price
supported: freshThe required price or no-charge status is explicit before commitment.
MongoDB Atlas details explicit pricing across tiers on its public pricing page, including $0/hour for Free forever, $0.011/hour for Flex, and $0.08/hour for Dedicated clusters.
Machine-operable checkout unknown
supported: freshMachine-operable checkout has not been established.
The retained account sign-up evidence does not provide enough interaction data to confirm or deny a machine-operable payment/checkout flow.
Sales-free purchase unknown
supported: freshWhether sales intervention is required has not been established.
Evidence from the account register target is insufficient to verify whether the complete purchase/checkout funnel requires sales intervention.
Supported payment rail unknown
supported: freshA supported payment rail has not been established.
The available registration page DOM evidence does not detail specific supported payment rails for checkout.
Provision
ReadyUsable credentials or delegated access are delivered through a documented flow.
Automatic activation has not been established.
A bounded provisioning delay has not been established.
Provisioning exposes machine-readable progress, terminal states, and reconciliation.
Evidence and actions
Automatic activation unknown
supported: freshAutomatic activation has not been established.
Retained evidence describes cluster and organization creation API endpoints but does not document whether onboarding automatically activates usable access without manual vendor intervention.
Bounded provisioning delay unknown
supported: freshA bounded provisioning delay has not been established.
The retained documentation does not specify an explicit, documented time bound for completing cluster provisioning.
Credential delivery
supported: freshUsable credentials or delegated access are delivered through a documented flow.
Documentation explicitly outlines supported authentication methods including Service Accounts with OAuth 2.0 and API Keys with HTTP Digest Authentication.
Machine-readable provisioning status
supported: freshProvisioning exposes machine-readable progress, terminal states, and reconciliation.
The API exposes machine-readable operation status endpoints, such as returning the status of all cluster operations.
Operate
ReadyA 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: unknownAn agent protocol interface has not been established.
API or tool access
supported: freshA documented API or tool interface is available for operation.
The MongoDB Atlas Administration API provides a documented RESTful interface supporting JSON entities over HTTPS to manage Atlas resources.
Delegated recovery
supported: freshCredential rotation, revocation, retry, and recovery paths are documented within delegated authority.
MongoDB Atlas documents delegated recovery and management mechanisms, including secret rotation, token revocation, and access list removal.
Documented limits and errors
supported: freshLimits, structured errors, retry behavior, and idempotency semantics are documented where applicable.
The MongoDB Atlas Administration API documentation details standard HTTP response codes, structured JSON error bodies, and rate limiting rules.
Usable authentication
supported: freshAuthentication is documented and usable within an agent authorization boundary.
The API supports standard OAuth 2.0 Client Credentials authentication using service account client IDs and secrets to issue scoped tokens.
What works
- Sign up: A stable signup entrypoint is available.
- Pay: The required price or no-charge status is explicit before commitment.
- Provision: Usable credentials or delegated access are delivered through a documented flow.
- Operate: A documented API or tool interface is available for operation.
What blocks agents
- Evaluate: Only part of the applicable terms is machine-readable.
Improve the report
Correct it, rerun it, or improve the funnel
Every request carries the exact profile revision, projection, declaration, and Catalog release.
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_01kzf0m4xb4p2kv9d7n6ts3c8y
- Revision
- sha256:e7526381235601b532f63c8c6dcb357f8b3cb7dc617da9ada397d6da5e60c6c9
- Projection
- sha256:061427fe494745a144ca7e7e53761eceeac69df4cfa5121764dac9fe2b87fb36
- Policy
- service-lifecycle-2026-08-08-calibrated: sha256:334e56852b5c38e178fcea839cfba680fb82dd96693842d933776baed21d63df
- Base Catalog release
- sha256:5082ec07047a2324648f569d234cc64342ce2707b2f3d77fde8fc06af517cee6