# gRPC Health Checker (`junipr/grpc-health-checker`) Actor

Check gRPC service health using standard health-check semantics and emit endpoint/service-level status rows, latency, errors, TLS details, and service availability summaries.

- **URL**: https://apify.com/junipr/grpc-health-checker.md
- **Developed by:** [junipr](https://apify.com/junipr) (community)
- **Categories:** SEO tools, Developer tools, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $6.50 / 1,000 endpoint testeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## gRPC Health Checker

### Store Positioning

**Store title:** gRPC Health Checker

**Short description:** Check gRPC service health using standard health-check semantics and emit endpoint/service-level status rows, latency, errors, TLS details, and service availability summaries.

**SEO title:** gRPC Health Checker — API, schema, and developer QA

**SEO description:** Check gRPC service health using standard health-check semantics and emit endpoint/service-level status rows, latency, errors, TLS details, and service availability summaries. Use it to catch contract drift, schema mistakes, unsafe endpoint assumptions, and developer-tool quality issues before release.

**Categories:** SEO\_TOOLS, DEVELOPER\_TOOLS, AUTOMATION

**Keywords:** grpc, health, checker, api/developer qa

### Fixed-Inclusive PPE Pricing

This actor uses pay-per-event pricing. Event prices include Apify platform usage; users are not expected to pay a separate platform-usage pass-through charge for the configured pricing model.

- Tier: A1 — API/developer QA
- Primary event: `endpoint-tested` at $0.00650 base
- Default max charge: $10.00
- Store discounts: FREE/BRONZE base, SILVER discounted, GOLD deepest approved discount

Event set:

- `actor-start`: base $0.00500, GOLD $0.00400. Grpc Health Checker: charged when actor start is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
- `endpoint-tested`: base $0.00650, GOLD $0.00520. Grpc Health Checker: charged when endpoint tested is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
- `contract-rule-checked`: base $0.00390, GOLD $0.00312. Grpc Health Checker: charged when contract rule checked is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
- `report-generated`: base $0.05000, GOLD $0.04000. Grpc Health Checker: charged when report generated is completed. The price includes Apify platform usage; no separate usage pass-through is intended.

### Public Task Concepts

- Validate gRPC Health Checker before release
- Run a bounded gRPC Health Checker QA check
- Audit grpc issues across supplied public inputs
- Extract evidence-backed grpc rows for client QA
- Generate developer QA evidence for gRPC Health Checker

Checks supplied-input standard gRPC health responses for whole-server and named services while preserving service names, status codes, latency, TLS settings, and redacted metadata usage.

### Inputs

- `endpoints`
- `serviceNames`
- `useTls`
- `plaintext`
- `authorityOverride`
- `metadataHeaders`
- `deadlineMs`
- `includeOverallServerCheck`
- `includeWatchProbe`
- `maxServicesPerEndpoint`
- `timeoutMs`
- `maxChargeUsd`

### Outputs

Dataset fields: `endpoint`, `serviceName`, `checkType`, `tlsEnabled`, `authority`, `healthStatus`, `grpcStatusCode`, `grpcStatusMessage`, `latencyMs`, `deadlineMs`, `metadataUsed`, `errorType`, `warning`, `passed`.

Reports: `grpc-health-check-report.md`, `grpc-service-health-results.csv`, `unhealthy-grpc-services.json`, `grpc-endpoint-summary.json`, `grpc-health-errors.json`.

Use small capped runs first; live network checks should stay bounded and avoid secrets in inputs.

# Actor input Schema

## `endpoints` (type: `array`):

Endpoints controls gRPC Health Checker processing for the supplied inputs; keep values conservative for first runs.

## `serviceNames` (type: `array`):

Service Names controls gRPC Health Checker processing for the supplied inputs; keep values conservative for first runs.

## `useTls` (type: `boolean`):

Use TLS controls gRPC Health Checker processing for the supplied inputs; keep values conservative for first runs.

## `plaintext` (type: `boolean`):

Supplied plaintext to analyze directly.

## `authorityOverride` (type: `string`):

Authority Override controls gRPC Health Checker processing for the supplied inputs; keep values conservative for first runs.

## `metadataHeaders` (type: `object`):

Metadata Headers controls gRPC Health Checker processing for the supplied inputs; keep values conservative for first runs.

## `deadlineMs` (type: `number`):

Maximum time in milliseconds allowed for the gRPC Health Checker operation before it is treated as timed out.

## `includeOverallServerCheck` (type: `boolean`):

Include overall server check in output rows or reports when available.

## `includeWatchProbe` (type: `boolean`):

Include watch probe in output rows or reports when available.

## `maxServicesPerEndpoint` (type: `number`):

Maximum services per endpoint to process in one run; keep defaults low for safe first runs.

## `timeoutMs` (type: `number`):

Maximum time in milliseconds allowed for the gRPC Health Checker operation before it is treated as timed out.

## `maxChargeUsd` (type: `number`):

Maximum estimated PPE charge allowed for the run before the actor stops gracefully.

## Actor input object example

```json
{
  "endpoints": [
    "grpcb.in:443"
  ],
  "serviceNames": [
    "catalog.CatalogService"
  ],
  "useTls": true,
  "plaintext": false,
  "authorityOverride": "grpcb.in",
  "metadataHeaders": {},
  "deadlineMs": 1000,
  "includeOverallServerCheck": true,
  "includeWatchProbe": false,
  "maxServicesPerEndpoint": 5,
  "timeoutMs": 5000,
  "maxChargeUsd": 1
}
```

# Actor output Schema

## `results` (type: `string`):

Rows in the default dataset.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("junipr/grpc-health-checker").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("junipr/grpc-health-checker").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call junipr/grpc-health-checker --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,junipr/grpc-health-checker"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/d6ytut8A9CORVM5md/builds/6ry0T4oExfki5knZb/openapi.json