canonical: https://jentic.com/apis/robtex.com/robtex

# Robtex Pro API

Premium API for DNS, IP, Lightning Network, and network intelligence data. The API exposes 63 endpoints secured with apiKey authentication.

## For AI agents

Programmatically get latest lightning network channels, check ip reputation against 100+ blocklists. Covers 63 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for cloud infrastructure only.

## Capabilities

- Get latest Lightning Network channels
- Check IP reputation against 100+ blocklists
- Lookup DNS records for a hostname
- Find hostnames using a DNS record value
- Monitor Robtex Pro API operational status and events

## Use cases

### Cloud Infrastructure Operations

Use the Robtex Pro API to perform cloud infrastructure operations programmatically. The API provides 63 endpoints covering core functionality including get latest lightning network channels, check ip reputation against 100+ blocklists, lookup dns records for a hostname.

Example prompt: Call GET /latest_lightning_channels to get latest lightning network channels

### Automated As_Info Management

Automate as_info operations by combining multiple Robtex Pro API endpoints. Agents can check ip reputation against 100+ blocklists and then lookup dns records for a hostname in a single workflow.

Example prompt: Call GET /ip_reputation to check ip reputation against 100+ blocklists, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Robtex Pro API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'get latest lightning network channels', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/latest_lightning_channels` | Get latest Lightning Network channels |
| GET | `/ip_reputation` | Check IP reputation against 100+ blocklists |
| GET | `/lookup_dns` | Lookup DNS records for a hostname |
| GET | `/reverse_lookup_dns_records` | Find hostnames using a DNS record value |
| GET | `/reverse_lookup_mx` | Find hostnames using a mail server |
| GET | `/reverse_lookup_ns` | Find hostnames using a nameserver |
| GET | `/reverse_lookup_ip` | Find hostnames pointing to an IP |
| GET | `/historic_reverse_lookup_ns` | Find hostnames that previously used a nameserver |

## Key resources

- **As_Info** — Operations for as_info
- **As_Prefixes** — Operations for as_prefixes
- **Asquery** — Operations for asquery
- **Bitcoin_Address_Transactions** — Operations for bitcoin_address_transactions
- **Bitcoin_Blockchain_Stats** — Operations for bitcoin_blockchain_stats

## Why Jentic

- **Setup:** Wiring the Robtex Pro API by hand means passing its RapidAPI proxy secret in the X-RapidAPI-Proxy-Secret header on every DNS and IP lookup and handling the request plumbing yourself. Through Jentic you install once, import the Robtex Pro API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** The Robtex Pro API is read-only lookups whose target travels in the request, so limit the agent to the operations it needs, such as forward DNS lookup or IP reputation, rather than granting the whole set. You choose which lookups it may call, and it can run only those.
- **Credential handling:** Your Robtex Pro API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'look up DNS records for a host' or 'check IP reputation', and Jentic returns the matching Robtex Pro API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Amazonaws** — Alternative cloud infrastructure API
- **Azure** — Alternative cloud infrastructure API
- **Googleapis** — Complementary cloud infrastructure API
- **Digitalocean** — Complementary cloud infrastructure API

## FAQ

### What authentication does the Robtex Pro API use?

The Robtex Pro API uses an API key passed in the `X-RapidAPI-Proxy-Secret` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I get latest lightning network channels with the Robtex Pro API?

Yes. Use the GET /latest_lightning_channels endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Robtex Pro API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I get latest lightning network channels through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get latest lightning network channels'. Jentic returns the matching Robtex Pro API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Robtex Pro API have?

The Robtex Pro API exposes 63 endpoints covering as_info, as_prefixes, asquery operations.

### Can I limit what my agent is allowed to do with the Robtex Pro API?

Yes. Because you run Jentic One yourself, your own rules decide which Robtex operations and which stored API key the agent may use. The Robtex Pro API is entirely read-only lookups, so you can grant just the calls the agent needs, such as forward DNS lookup or IP reputation, and hold back the rest of the 63 endpoints. The agent can only invoke the lookups you have allowed.