What authentication does the blocky API use?

The Blocky REST API itself has no authentication scheme defined in the spec - it is intended to listen on a trusted local network or behind a reverse proxy. When you call it through Jentic, the resolver's base URL and any reverse-proxy credentials (such as a shared API key or basic-auth header you have placed in front of Blocky) are stored encrypted in your Jentic One instance and injected at execution time, so they never appear in the agent's prompt or logs.

Can I pause ad-blocking for just one group of devices with the blocky API?

Yes. The GET /blocking/disable endpoint accepts a 'duration' query parameter (for example 5m, 1h, or 5m30s) and a 'groups' query parameter as a comma-separated list of group names. Only the named groups are disabled; if you omit 'groups', all groups are disabled. After the duration elapses, blocking automatically re-engages, and you can inspect the remaining time via GET /blocking/status.

What are the rate limits for the blocky API?

Blocky does not document rate limits in its OpenAPI spec, and because it runs as a self-hosted resolver on your own hardware (Docker, Raspberry Pi, or Kubernetes), the practical ceiling is whatever your host can handle. For control-plane endpoints like /lists/refresh and /cache/flush, treat them as occasional maintenance calls rather than per-request operations - refreshing block lists is I/O heavy and is typically done on a schedule, not on every event.

How do I run a test DNS query through blocky API using Jentic?

Search Jentic for 'run a DNS query through blocky', load the 'query' operation, and execute it with a body like {"query": "example.com", "type": "A"}. The response includes the return code, the response itself, the responseType (such as CACHED or BLOCKED), and Blocky's internal reason - useful for diagnosing whether a domain was filtered by a deny list or resolved upstream. Install with pip install jentic to call this from Python.

Is the blocky API free to use?

Yes. Blocky is open source under the Apache 2.0 license and is free to self-host. There are no per-call fees because the API runs on your own infrastructure; your only costs are the hardware and bandwidth you provide.

How do I refresh Blocky's deny lists without restarting the resolver?

Call POST /lists/refresh through Jentic. Blocky reloads all configured allow and deny lists in place and returns 200 on success or 500 with a plain-text error body if a source could not be fetched. Because the resolver does not restart, the DNS cache and active connections are preserved.

Can I limit what my agent is allowed to do with the Blocky API?

Yes. Because Jentic One is self-hosted, you decide which of Blocky's control operations the agent can call and which credentials it uses. Since the API exposes operations rather than per-resource ids, you can allow read-only calls like checking blocking status or running a test DNS query while leaving out state-changing operations such as disabling blocking, refreshing lists, or flushing the cache.