monid discover

Search for data endpoints using natural language.

Usage

monid discover -q <query> [--limit <limit>] [--json]

Flags

Flag	Type	Required	Description
-q, --query <query>	string	Yes	A short natural language search query
--limit <limit>	number	No	Maximum number of results (max 10)
-j, --json	boolean	No	Output raw JSON

Examples

# Search for Twitter-related endpoints
monid discover -q "twitter posts"

# Search with a limit
monid discover -q "linkedin profiles" --limit 3

# Get raw JSON output
monid discover -q "amazon product reviews" --json

Output

Returns a list of endpoints matching the query:

Provider   Endpoint                       Price         Description
apify      /apidojo/tweet-scraper         $0.003/call   Scrape tweets by search...
apify      /apidojo/twitter-user-scraper  $0.003/call   Scrape Twitter user pro...

With the --json flag, the full JSON response is printed:

{
  "results": [
    {
      "provider": "apify",
      "providerName": "Apify",
      "endpoint": "/apidojo/tweet-scraper",
      "description": "Scrape tweets by search terms, hashtags, or user handles",
      "price": {
        "type": "PER_CALL",
        "amount": 0.003,
        "currency": "USD"
      }
    }
  ],
  "query": "twitter posts",
  "count": 2
}

Tips

• Keep queries short and focused. Noun phrases like "twitter posts" or "amazon product prices" work better than full sentences.
• Break complex requests into smaller pieces. If you need data from multiple sources, discover each separately.
• The endpoint catalog grows continuously. Always discover rather than assuming what's available.

Next Steps

After discovering endpoints, use monid inspect to see the full input schema before running.