What authentication does the Host.io API use?

Three options are supported: bearer token (Authorization: Bearer <token>), HTTP basic, or an API key in the query string. Jentic stores the credential in your Jentic One instance and injects whichever scheme the call requires.

Can I find every domain hosted on a given IP with the Host.io API?

Yes. GET /domains/{field}/{value} with field=ip and the IP address as the value returns the list of domains observed on that IP. The same path supports field=ns, mx, asn, and backlink for other reverse lookups.

What are the rate limits for the Host.io API?

Host.io rate limits are tied to plan tier - free plans are heavily throttled and paid plans scale up to thousands of requests per day. Check your plan in the Host.io dashboard and back off on 429 responses.

How do I look up DNS records for a domain with the Host.io API through Jentic?

Run pip install jentic, search for 'get DNS records for domain', load the GET /dns/{domain} schema, and execute. Jentic handles the auth header and returns the structured DNS payload.

Does the Host.io API give me both backlinks and outbound links?

Yes. The /full/{domain} endpoint returns scraped website metadata (title, description, outbound links sample) and backlink counts in a single response, so an agent can pull both link directions in one call.

Can I limit what my agent is allowed to do with the Host.io API?

Yes. Because you run Jentic One yourself, your own rules decide which Host.io operations and credentials the agent may use, so you can allow only the lookups it needs, such as GET /web/{domain} for a website profile, GET /dns/{domain} for DNS records, or GET /domains/{field}/{value} for a reverse lookup by IP, NS, MX, or ASN. Every Host.io operation is a read, so nothing it calls mutates any data. Keep the reverse-lookup and full-report endpoints out of the allowed set if the agent only needs single-domain DNS or metadata.