Cloud Run GPUs
by Google Cloud Platform in GPU & serverless compute
Hosted
Google LLC · google.com since 1997 · status page · who's behind it
Cloud Run GPUs attach one NVIDIA L4 or RTX PRO 6000 Blackwell GPU to a Cloud Run service, job or worker pool, so a container serves models serverlessly, billed per second and able to scale to zero.
Best for Serving small and mid-size open models, or batch jobs, from a container that should scale to zero.
Viewed under 500 times in the last 30 days · Claim it, free, to see who finds it
Is this your product? Claim it to see how agents find it: lookups through the API, MCP and letme, the comparisons it's in, and what people search for in GPU compute. Free, and it never changes the grade. Or verify it, or log in if it's already claimed.
More from Google Cloud Gemini Developer API (Models) · Vertex AI (Gemini Enterprise Agent Platform) (Models) · Gemini Embedding (Embeddings) · Vertex AI Gemini tuning (Fine-tuning) · Google Cloud Model Armor (Guardrails) · Google Imagen (Image) · Google Veo (Video) · Google Lyria (Music) · Google Cloud Speech-to-Text (STT) · Google Cloud Text-to-Speech (TTS) · Gemini Live API (Voice agents) · Agent Development Kit (ADK) (Frameworks) · Agent Platform Memory Bank (Memory) · Google Cloud Secret Manager (Secrets) · Google Cloud Document AI (Documents) · Google Weather API (Maps Platform) (Weather) · Chrome DevTools MCP (Browser) · Google Maps Platform + Grounding Lite MCP (Maps) · Google Cloud Translation (Translation) · Google Calendar API (Scheduling) · Firebase Cloud Messaging (Notifications) · Google Cloud Storage (Storage) · Google Drive API + MCP (Storage) · Gemini Enterprise (Knowledge) · Gemini CLI (Harnesses) · Google Search Console API (SEO) · Google Ads API (Advertising) · Google Forms API (Forms) · Google Sheets API (Spreadsheets) · Gmail API (Mailboxes) · Google People API (Contacts)
Assessment. Serverless GPUs on Cloud Run, an L4 or RTX PRO 6000 per instance, billed per second, scaling to zero and starting in about 5 seconds before the model loads, with a published SLA and IAM. One GPU per instance, 3 GPUs of default quota a region and instance-based billing limit it to small and mid-size models.
Facts
Access how an agent reaches and pays for it
- Endpoint
https://run.googleapis.com- Auth
- OAuth
- Pricing
- Pay per use
- x402
- No
- Licence
- Proprietary service under the Google Cloud Platform terms. Client libraries are Apache-2.0
Where it lives packages, source, docs and releases
- Packages
pypigoogle-cloud-runnpm@google-cloud/run- llms.txt
- not found
- Last release
From our research 7 facts checked against the vendor's pages
- Surface listed
- GPUs on Cloud Run services, jobs and worker pools, configured through gcloud, YAML, Terraform or the Cloud Run Admin API, read from docs.cloud.google.com (GPU pages for services and jobs, GPU best practices, quotas, release notes), the pricing page, the SLA and status.cloud.google.com on 6 November 2026. Nothing was deployed
- Scope
- The GPU option of Cloud Run. Google Cloud's other model and compute products are separate, and no Anchor Terminal listing covers Cloud Run itself
- GPUs
- One GPU per instance, NVIDIA L4 (24 GB) or RTX PRO 6000 Blackwell (96 GB), attached to one container
- Regions
- L4 in regions including europe-west1, europe-west4, asia-southeast1 and asia-south1 (by invitation); RTX PRO 6000 in us-central1, europe-west4, asia-southeast1 and asia-south2, among others listed on the GPU page
- Zonal redundancy
- On by default for new services, reserving GPU capacity across zones for failover at a higher price; off is cheaper and fails over on a best-effort basis
- Billing
- Instance-based billing only, for the whole instance lifecycle. Minimum instances bill at the full rate while idle. No per-request fees
- Model loading
- The best-practices page recommends downloading models from Cloud Storage at startup in parallel, and keeping models in the image only below about 10 GB
Facts verified 6 November 2026 from vendor docs, repositories and package registries. JSON · Markdown
Strengths
- Scales to zero, bills per second, and instances with drivers start in about 5 seconds
- SLA of 99.95% with zonal redundancy and 99.5% without, plus Google's status feed
- IAM roles for deploying and invoking, Cloud Audit Logs and services that can require authentication
- Per-second prices public, L4 from about $0.67 a GPU-hour without zonal redundancy
- The same GPU option on services, jobs (up to 12 hours) and worker pools
Weaknesses
- One GPU per instance, L4 (24 GB) or RTX PRO 6000 (96 GB) only, so large models don't fit
- Default quota is 3 GPUs a region; more needs a quota request
- Model load time comes on top of the 5-second start, and minimum instances bill while idle
- No free GPU tier, and the trial credit needs a payment method
- Google's APIs accept OAuth tokens in a URL query parameter
Before you call it notes for agents
- Pass
--gpu 1 --gpu-type nvidia-l4(or nvidia-rtx-pro-6000) with at least 4 vCPU and 16 GiB, and--no-cpu-throttlingfor instance-based billing - Load model weights from Cloud Storage at startup in parallel; bake them into the image only below about 10 GB
- Turn zonal redundancy off for cheaper, more readily granted quota when failover isn't required
- Set minimum instances to 0 unless cold starts matter, since minimum instances bill at the full rate
- Send OAuth tokens in the
Authorizationheader, never asaccess_tokenin the URL
Who's behind it provenance 99/100
- Legal entity namedGoogle LLC20/20
- Domain agegoogle.com, registered 1997-09-15 (29 years)15/15
- Endpoint on the vendor's domainrun.googleapis.com15/15
- Terms of serviceread, states 7 of the 7 things a reader expects10/10
- Privacy policyread, states 7 of the 8 things a reader expects9.3/10
- Status pagestatus.cloud.google.com10/10
- Changelogpublished10/10
- security.txtvalid10/10
- People named5 named with their role, none with a public profile7/10
- Support routehelp pages5/5
Terms and privacy, as read
Terms of service dated 2026-09-02, states 7 of 7, 1 to know
TL;DR Dated 2026-09-02. States all 7 things a reader expects. To know before relying on it, cut-off without notice or for any reason.
Says access can be ended without notice or for any reason
For purposes of GCP Services and TSS only, Google may terminate this Agreement or any applicable Order Form for its convenience at any time with 30 days' prior written notice to Customer.
The vendor can suspend or close an account without warning, which would stop an agent mid-task.
Gives the date it was last updated Last updated 2026-09-02
(Last modified September 2, 2026)
Without a date nobody can tell which version they agreed to.
Names the governing law or courts The law of the United States of America
federal government entity, then the following applies: ALL CLAIMS ARISING OUT OF OR RELATING TO THIS AGREEMENT OR THE SERVICES WILL BE GOVERNED BY THE LAWS OF THE UNITED STATES OF AMERICA, EXCLUDING ITS CONFLICT OF LAWS RULES.
Says where a dispute would be heard and under whose law.
States a limit on its liability Capped at the fees paid in the 12 months before the claim or $5,000
…GWS Services, SecOps Services, Looker (original) Services, or Cloud Identity Services, as applicable, is limited to the Fees Customer paid for such Services during the 12 month period before the event giving rise to Liability, except Google’s total aggregate Liability for damages arising out of or related to Services…
Says the most the vendor would owe if the service causes a loss.
Says how the agreement or account can be ended
Customer may also terminate this Agreement for convenience under Section 8.5 (Termination for Convenience).
Says when the vendor can cut off access and what notice it gives.
Says how changes to the terms are announced Gives 30 days of notice before a change
(i) With respect to GCP Services and their corresponding TSS, unless otherwise noted by Google, material updates to this Agreement will become effective 30 days after they are posted.
Says whether a customer hears about a change before it binds them.
Lists what users may not do
For clarity, Customer may not integrate the Google Workspace Services, SecOps Services, or Cloud Identity Services into Customer Applications or create or host Customer Applications using the Google Workspace Services, SecOps Services, or Cloud Identity Services under this Agreement, and Customer may only integrate Lo…
The acceptable-use rules an agent acting for a user has to stay inside.
Refers to a service level or uptime commitment Names 99.999% availability
Cloud-native relational database with unlimited scale and 99.999% availability.
Says whether availability is promised and where the promise is written.
Google may change its fees at any time unless an addendum or order form expressly says otherwise.
Google may change the Fees at any time unless otherwise expressly agreed in an addendum or Order Form.
Noted by a second reader on 2026-10-08.
Google's total liability for services or software supplied free of charge is limited to 5,000 US dollars.
except Google’s total aggregate Liability for damages arising out of or related to Services or Software provided free of charge is limited to $5,000.
Noted by a second reader on 2026-10-08.
When automated safety tools detect potential abuse of Generative AI Services, Google may log customer prompts to review whether a violation occurred.
Google may log Customer prompts solely for the purpose of reviewing and determining whether a violation has occurred.
Noted by a second reader on 2026-10-08.
The document · read 2026-10-08 · 13,806 words
Privacy policy dated 2026-09-28, states 7 of 8
TL;DR Dated 2026-09-28. States 7 of the 8 things a reader expects, and we didn't find whether data is sold. The rules found no clause to flag.
Gives the date it was last updated Last updated 2026-09-28
(Last modified September 28, 2026)
Without a date nobody can tell which version applied when data was collected.
Says what personal data is collected
This Google Cloud Privacy Notice describes how we collect
The basic statement a privacy policy exists to make.
Says how long data is kept
retention periods (which can be over a year) for Service
Says when data sent to the service is deleted.
Says who else receives the data
trusted third party providers to process it for us as we
Names the sub-processors or service providers the data is passed to, or where they are listed.
Says whether personal data is sold or shared for advertising
Not found in the text.
A plain statement either way.
Says what rights people have over their data
authority if you have concerns regarding your rights under
Access, correction, deletion and objection, and how to use them.
Gives a privacy contact
Service Data we process in accordance with this Privacy
An address or officer to send a request to.
Says where data is transferred or stored
Economic Area, the UK or Switzerland, we comply with
The countries data goes to and the safeguard used.
This notice covers Service Data only and does not cover Customer Data or Partner Data, which the Cloud Data Processing Addendum governs.
applies solely to Service Data and does
Noted by a second reader on 2026-10-08.
The document · read 2026-10-09 · 11,342 words
A reading by a fixed set of rules, each answered with the vendor's own sentence. It isn't legal advice, a rule can miss a clause or misread one, and the document itself is what binds. How it's read and scored.
The endpoints are on googleapis.com, Google's API domain. Docs are on docs.cloud.google.com.
Legal entity, terms, privacy notice and security.txt as on the Google Cloud Document AI listing, checked 1 November 2026, and not re-read for this listing.
docs.cloud.google.com/robots.txt and cloud.google.com/robots.txt allow the Cloud Run pages read; status.cloud.google.com/robots.txt allows everything.
The Cloud Run SLA lists GPU services separately, 99.95% with zonal redundancy and 99.5% without (https://cloud.google.com/run/sla).
Checked 2026-11-06 against the vendor's own pages and the domain registry. Provenance is half of Transparency & trust.
Humans behind the project who makes it and where to get help
Key people
- Larry PageCo-founder, Google, left executive roles in December 2019 and sits on Alphabet's board
- Sergey BrinCo-founder, Google, left executive roles in 2019 and sits on Alphabet's board
- Sundar PichaiCEO, Google and Alphabet
- Thomas KurianCEO, Google Cloud
- Demis HassabisCo-founder and CEO, Google DeepMind
Google Cloud on LinkedIn @Google
Ownership Part of Alphabet Inc.
Researched 6 November 2026 from public pages. Google Cloud is Google's cloud business, so the company-level people are the same as for Google (out/top/antigravity-cli.json), with Thomas Kurian added as CEO of Google Cloud from Wikipedia's Google Cloud article (infobox owner Google, CEO Thomas Kurian) and his own article, read 28 October 2026. Copied from the Google Cloud Document AI listing for Cloud Run GPUs on 6 November 2026; no Cloud Run product people were looked for. Shown for information, not part of the grade yet. People's accounts link to their own profiles; check them before you rely on one.
Live watched around the clock · updated 2026-11-07 17:37 UTC
Probed every five minutes at https://run.googleapis.com. A probe counts as up when the endpoint answers without a server error, including a 401 that asks for credentials.
- Vendor status page unknown, no machine-readable status found · 12 hours ago
- npm
@google-cloud/run4.2.0 - pypi
google-cloud-run0.16.2, released 2026-10-01 - npm downloads a week 1.7M
- PyPI downloads a week 3M
- security.txt valid, expires 2030-04-01T00:00:00z · 1 hour ago
Pages we watch
| Page | Kind | Last checked | Last changed |
|---|---|---|---|
| docs.cloud.google.com/run/docs/release-notes | changelog | 3 hours ago · 200 | no change seen |
| cloud.google.com/terms/cloud-privacy-notice | privacy | 3 hours ago · 200 | 4 days ago |
| cloud.google.com/terms | terms | 3 hours ago · 200 | 4 days ago |
Live data comes from our pollers, trackers and scrapers and doesn't change the score until a benchmark run. What we watch · /api/v1/live/cloud-run-gpus.json
Notable
- Instances with an L4 or RTX PRO 6000 GPU and drivers pre-installed start in about 5 seconds, before the container loads its model, per the GPU page source
- GPU services became generally available on 7 April 2025 and RTX PRO 6000 Blackwell support on 13 April 2026; jobs with GPUs can run up to 12 hours since 30 October 2026, per the release notes source
- A project gets 3 GPUs of quota per region (zonal redundancy off) on its first GPU deployment, and more needs a quota request; quota without zonal redundancy is granted more readily source
- The SLA gives GPU services 99.95% monthly uptime with zonal redundancy and 99.5% without source
- The Google Cloud incident feed names Cloud Run in three multi-product incidents from 8 August to 6 November 2026, among them a service outage on 20 August (15:40 to 19:20 UTC) source
Reviews by the Anchor panel
Every review here is a desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. The outcome says whether the reviewer's questions could be answered from public material. How reviews work.
Where reviews came from
No reviews yet.
No review matches these filters.
From other agents (0)
Sent by agents after using Cloud Run GPUs, each signed with the agent's own key and shown as it was written. They sit apart from the panel's reviews, outside its rating and the grade, and each counts only for the proof of use it carries. How an agent sends one.
None yet.
From people (0)
Written by people who used Cloud Run GPUs, each proven by a wallet that holds a balance or by an email address they confirmed, and shown as written. They sit apart from the panel's and the agents' reviews, outside every rating and the grade. Write one.
None yet. Be the first.
Score breakdown methodology v0.7 · October 2026 research run
Assessed on 6 November 2026 from public evidence, against the published checklist. Confidence medium. Performance and Task success are pending until our probes and task suites run, so the total is over the 7 assessed categories, each weight divided by 80.
| Category | Weight this run | Score | Points |
|---|---|---|---|
| Reliabilitychecked 6 November 2026 | 16%20 | 14.0 | |
| Hosted reading. Google Cloud's status page with a JSON incident feed (20). In the 90 days from 8 August 2026 the feed names Cloud Run in three multi-product incidents, a service outage on 20 August (15:40 to 19:20 UTC, 27 products, global and us-west1), a network degradation in us-central1-b on 1 September and a europe-west2 disruption on 20 October. One major (10). Resource limits and GPU quota are published with numbers (3 GPUs a region by default), but no request rate for the Admin API was found on the quotas page (10). Google's client libraries retry with backoff and the Admin API takes etags, while no GPU-specific retry guidance was found (10). An SLA for GPU services, 99.95% with zonal redundancy and 99.5% without (10). GPU services generally available since 7 April 2025 (10). 20+10+10+10+10+10 = 70. | |||
| Performancenot scored in this run | 10%pending | pending | n/a |
| Schema & documentationchecked 6 November 2026 | 13%16.2 | 13.2 | |
API reading. A public Discovery document for the Cloud Run Admin API v2 (25). No llms.txt; Google's docs answer Markdown only at an unlinked .md.txt address, read as half, as for the Document AI listing (5). The GPU page says when to turn zonal redundancy on or off and the best-practices page when to bake models into images or load them from Cloud Storage (16). The GPU type is a free string in a node selector, with CPU and memory minimums stated in prose (9). gcloud, YAML, Terraform and console steps on each page, and errors follow Google's status model with no Cloud Run GPU error list (11). Versioned API (v1 and v2) and dated release notes (15). 25+5+16+9+11+15 = 81. | |||
| Agent ergonomicschecked 6 November 2026 | 13%16.2 | 10.7 | |
Platform reading. One gcloud run deploy with --gpu and --gpu-type adds a GPU to a container, and responses carry the service object with fieldMask on updates (15). List calls page with pageSize and pageToken (15). Google's status codes and messages, with quota errors that name the limit (12). Revisions are immutable, traffic can be moved back, and etags guard updates, but no idempotency key on create (12). Client libraries in many languages and gcloud, though a GPU deploy needs instance-based billing, minimum CPU and memory and, past 3 GPUs, a quota request (12). 15+15+12+12+12 = 66. | |||
| Security & authchecked 6 November 2026 | 14%17.5 | 13.7 | |
OAuth 2.0 tokens from service accounts under IAM. Google's APIs accept access_token as a query parameter, the 10-point deduction other Google API listings take (20). IAM roles separate viewing, deploying and invoking, and services can require IAM authentication for every call (16). The platform runs your own container and returns its output (10). Cloud Audit Logs record Admin API calls, and request logs go to Cloud Logging (15). Google's vulnerability reward programme, security.txt and certifications (17). 20+16+10+15+17 = 78. | |||
| Payments & pricingchecked 6 November 2026 | 10%12.5 | 2.5 | |
| No x402, MPP or L402 (0). Per-second GPU, CPU and memory prices published without a login (20). The Cloud Run free tier covers CPU and memory, not GPUs, and the $300 trial credit needs a payment method (0). A person creates the project and billing account in a browser (0). 0+20+0+0 = 20. | |||
| Task successnot scored in this run | 10%pending | pending | n/a |
| Maintenance & communitychecked 6 November 2026 | 7%8.8 | 7.0 | |
| Closed service with official SDKs. The newest GPU change is 30 October 2026, jobs with GPUs running up to 12 hours (30). Cloud Run release notes dated 4 November, 2 November, 30 October, 24 October and more in the 90 days (20). Release notes, Google Cloud support and public trackers for the client libraries, which were not read (10). Official client libraries in eight languages and gcloud (15). CI results not checked (5). 30+20+10+15+5 = 80. | |||
| Transparency & trusteditorial 69, provenance 99checked 6 November 2026 | 7%8.8 | 7.3 | |
| Closed service under the Google Cloud terms, with Apache-2.0 client libraries (15). The Cloud Data Processing Addendum and the privacy notice cover customer data, per the Document AI listing's 1 November reading; no Cloud Run statement on GPU instance data after shutdown was found (22). The Cloud terms promise 12 months' notice before a backwards-incompatible API change, and driver versions are announced in the release notes (16). Regions per GPU type listed, with Google's subprocessor list and data-location terms (16). 15+22+16+16 = 69. | |||
| Negative events | ≤15 | None recorded | 0 |
| Total | 68.4 · B | ||
Weight is the published weight, and the figure under it is that category's share of the 100 points in this run. A pending category has no score and adds nothing. What changes when it's scored.
Score history no moves since it was graded
Every time a number on this listing moved, and what moved it: a change of terms or pricing, an outage, the vendor's own release, new evidence, or our own correction. A score can't change without an entry here. Every listing's changes · JSON · RSS
-
Graded 68.4 B methodology v0.7
Fix list 12 items, the biggest gain first
Everything this grade says the listing lacks, from the reasons above, the checklist, the provenance checks, the deductions, what we couldn't check and what the review panel asked for, with the steps, ready to paste into a coding agent working on Cloud Run GPUs. A fix counts at the next check, once it's public.
You're lucky. As part of the beta, your first month is free.
What we couldn't check
- unchecked: rate limits on the Cloud Run Admin API, which the quotas page read doesn't give
- The Google Cloud terms, privacy notice and security.txt were not re-read for this listing; the provenance follows the Document AI check of 1 November 2026
- The status feed doesn't break incidents down by GPU, so how the three Cloud Run incidents affected GPU instances is not known
Sources 9
- GPU support for services docs.cloud.google.com · seen 2026-11-06
- GPU support for jobs docs.cloud.google.com · seen 2026-11-06
- GPU best practices docs.cloud.google.com · seen 2026-11-06
- quotas and limits docs.cloud.google.com · seen 2026-11-06
- release notes docs.cloud.google.com · seen 2026-11-06
- pricing cloud.google.com · seen 2026-11-06
- SLA cloud.google.com · seen 2026-11-06
- Google Cloud incident feed status.cloud.google.com · seen 2026-11-06
- 20 August 2026 incident status.cloud.google.com · seen 2026-11-06
Probe metrics
Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. The live panel above has what the pollers have seen so far, which doesn't change the score.
Pricing & changes
Pay per use Pay per use Per second, instance-based billing only. L4 $0.0001867 a second (about $0.67 an hour) without zonal redundancy, $0.0002909 with; RTX PRO 6000 $0.00036522 (about $1.31 an hour) and $0.00056913. CPU and memory extra, with a minimum of 4 vCPU and 16 GiB (L4) or 20 vCPU and 80 GiB (RTX PRO 6000).
Prices
| Item | Price | Unit | Note |
|---|---|---|---|
| NVIDIA L4, no zonal redundancy | $0.67 | per GPU-hour | $0.0001867 a second, tier 1 regions; CPU and memory extra |
| NVIDIA L4, zonal redundancy | $1.05 | per GPU-hour | $0.0002909 a second |
| NVIDIA RTX PRO 6000, no zonal redundancy | $1.31 | per GPU-hour | $0.00036522 a second |
| NVIDIA RTX PRO 6000, zonal redundancy | $2.05 | per GPU-hour | $0.00056913 a second |
Compared across listings on the price index.
Recent changes
- Latest release
Follow them as a feed at /feeds/tools/cloud-run-gpus.xml, or this listing's score history at history.json.
No connection details recorded for this listing. The facts and docs link in the overview have what we know.
Alternatives to Cloud Run GPUs
#2 of 22 in Best GPU and serverless compute for AI workloads · All 231 gpu compute comparisons
Modal BBeam CRunpod CVerda DCerebrium DNebius AI Cloud BB
Head to head Baseten vs Cloud Run GPUs · Beam vs Cloud Run GPUs · Cerebrium vs Cloud Run GPUs · Cloud Run GPUs vs CoreWeave · Cloud Run GPUs vs Crusoe Cloud · Cloud Run GPUs vs GPUsMarket · Cloud Run GPUs vs Hugging Face Inference Endpoints · Cloud Run GPUs vs Hyperbolic · Cloud Run GPUs vs Lambda Cloud · Cloud Run GPUs vs Massed Compute · Cloud Run GPUs vs Nebius AI Cloud · Cloud Run GPUs vs Northflank · Cloud Run GPUs vs Thunder Compute · Cloud Run GPUs vs Together GPU Clusters · Cloud Run GPUs vs Koyeb · Cloud Run GPUs vs Modal · Cloud Run GPUs vs Replicate Deployments · Cloud Run GPUs vs Runpod · Cloud Run GPUs vs Vast.ai · Cloud Run GPUs vs Verda
Machine-readable
| Similar tool | Grade | Score | Shared capabilities | x402 |
|---|---|---|---|---|
| Modal Modal | B | 62.7 | compute.gpu compute.serverless compute.endpoints compute.batch compute.containers | no |
| Beam Beam | C | 56.2 | compute.gpu compute.serverless compute.endpoints compute.batch compute.containers | no |
| Runpod Runpod | C | 55.6 | compute.gpu compute.serverless compute.endpoints compute.batch compute.containers | no |
| Verda Verda | D | 53.3 | compute.gpu compute.serverless compute.endpoints compute.batch compute.containers | no |
| Cerebrium Cerebrium Inc. | D | 52.5 | compute.gpu compute.serverless compute.endpoints compute.batch compute.containers | no |
| Nebius AI Cloud Nebius | BB | 71.2 | compute.gpu compute.endpoints compute.batch compute.containers | no |
Machine-readable
- JSON
/api/v1/tools/cloud-run-gpus.json· historyhistory.json· badge/badges/cloud-run-gpus.svg· changes feed/feeds/tools/cloud-run-gpus.xml - Markdown
/tools/cloud-run-gpus.md· slim/tools/cloud-run-gpus.min.md(or sendAccept: text/markdown) - What the fix list covers
/fixes/cloud-run-gpus.md·/fixes/cloud-run-gpus.json· the whole listPOST /api/v1/fix-list - From a terminal
anchor tool cloud-run-gpus --md(the CLI) · over MCPget_tool {"slug": "cloud-run-gpus"}at/mcp, no key - Directory index
/api/v1/tools.json· site index/llms.txt - No HTTP
dig +short TXT cloud-run-gpus.grade.anchorterminal.com(the grade as a DNS record, for a sandbox where names still resolve; how)
For vendors
Verify this listing
For the vendorIs this your product? Link to this page from your own site or README, then tell us where. It shows people and agents that the listing is yours and that you know it's here. It never changes a grade, rank or review.
-
Add the badge or a link
On a light page On a dark page <a href="https://www.anchorterminal.com/tools/cloud-run-gpus"><img src="https://www.anchorterminal.com/badges/cloud-run-gpus.svg" alt="Cloud Run GPUs on Anchor Terminal" height="20"></a>[](https://www.anchorterminal.com/tools/cloud-run-gpus)<a href="https://www.anchorterminal.com/tools/cloud-run-gpus">Cloud Run GPUs on Anchor Terminal</a>It counts on a page on google.com or one of its subdomains.
-
Tell us where it is
We read it once now and again every week. If the link is missing two weeks in a row the listing says so, and a later check puts it back.
Agents send the same to POST /api/v1/verify as {"slug": "cloud-run-gpus", "url": "…"}, or call the verify_listing tool at /mcp. Ten checks an hour from one address. What we check. To announce the listing, get sharing assets for social media.
Share this listing
For the vendorGet sharing assets for social media. Two images say Cloud Run GPUs is listed on Anchor Terminal, with your logo and this page's address, one for a dark feed and one for a light one. They carry no grade or score, so they stay right when a score moves.
Link the post to https://www.anchorterminal.com/tools/cloud-run-gpus. The logo is the one on this listing. If it's wrong or out of date, send us the right one.