monid inspect - Monid

Get full details for a data endpoint, including input schema, pricing, and documentation.

Usage

monid inspect -p <provider> -e <endpoint> [--json]

Flags

Flag	Type	Required	Description
`-p, --provider <provider>`	string	Yes	Provider slug
`-e, --endpoint <endpoint>`	string	Yes	Endpoint name
`-j, --json`	boolean	No	Output as JSON

Examples

# Inspect a Twitter scraper
monid inspect -p apify -e /apidojo/tweet-scraper

# Inspect a Google Maps scraper
monid inspect -p apify -e /damilo/google-maps-scraper

# Get raw JSON output
monid inspect -p apify -e /apidojo/tweet-scraper --json

Output

The inspect command displays:

Provider and endpoint name
Description - what the endpoint does
Summary - detailed overview (when available)
Input - structured input schema (path params, query params, body)
Pricing - type, amount, flat fee, variants, tiers, and notes
Health - operational status and run time percentiles (when available)
Documentation URL - link to the provider’s docs
Notes - additional caveats or guidance

Example output:

Provider
  Apify (apify)

Endpoint
  /apidojo/tweet-scraper

Description
  Scrape tweets by search terms, hashtags, or user handles

Pricing
  Type:   PER_CALL
  Amount: $0.003

Health
  Status:   healthy
  Run time: 4.4s typical · 6.1s tail

Input
  Body
  {
    "searchTerms": ["string"],
    "maxItems": "number",
    "sort": "string"
  }

Documentation
  https://apify.com/apidojo/tweet-scraper

Always inspect before running. The input schema tells you exactly what parameters the endpoint accepts - never guess.

Next Steps

After inspecting an endpoint, use monid run to execute it.