Can I run a regex search across all Debian source code?

Yes. GET /search accepts an RE2 regex via the q parameter and searches every indexed Debian source file. For deduplicated package-level results, call /searchperpackage with the same query so the response groups matches by source package.

What are the rate limits for the Debian Code Search?

Debian Code Search does not publish a fixed public rate limit, but the service is operated by volunteers and enforces fair-use throttling. Back off on HTTP 429 responses and avoid running unbounded queries with very broad patterns.

How do I aggregate matches per package through Jentic?

Search Jentic for 'aggregate Debian code search matches per package', load the GET /searchperpackage schema, and execute it with the regex query. Jentic injects the x-dcs-apikey from the vault and returns one result per source package.

Does the Debian Code Search support full-text searches without regex?

All searches are RE2 regex queries. To match literal text, escape regex metacharacters before submitting the query - for example `strncpy\\(` to find calls to strncpy. The query language also supports filters such as path:, package:, and lang: to narrow the scope.

Can I limit what my agent is allowed to do with the Debian Code Search API?

Yes. Because you self-host Jentic One, your own rules decide which Debian Code Search operations and credentials the agent may use, so you can grant it just the regex search on GET /search, just the per-package aggregation on GET /searchperpackage, or both. Debian Code Search passes the query in request parameters rather than a resource id in the URL path, so you scope the agent by operation rather than by target, and it can only call the operations you allow. Both endpoints are read-only, so the operations you permit are the only ones that ever run.