Can I list a Halo 5 player's custom maps with this API?

Yes. Call GET /h5/players/{player}/mapvariants with the player's gamertag to list all map variants saved to their file share, and GET /h5/players/{player}/mapvariants/{variant} to retrieve a single variant's metadata.

What are the rate limits for the Halo UGC API?

Rate limits follow the Halo developer portal subscription tier (typically 10 requests per second on the standard tier) and are shared across all Halo APIs on the same key. Back off on HTTP 429 responses; the API does not return a Retry-After header.

How do I fetch a single Halo 5 game variant through Jentic?

Search Jentic for 'get halo 5 game variant', load the schema for GET /h5/players/{player}/gamevariants/{variant}, and execute with the player and variant IDs. Run pip install jentic and use the async client.search, client.load, and client.execute pattern.

Does the UGC API return the binary contents of map or game variants?

No. The API returns metadata only - variant ID, name, description, owner, and creation timestamps. The binary playable file is not exposed; players still need to download it in-game from the file share.

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

Yes. Because you run your own self-hosted Jentic One instance, your own rules decide which of the four Halo UGC operations the agent may call and which credentials it may use. You can scope the agent to only the operations it needs, such as GET /h5/players/{player}/mapvariants to list a player's map variants, while withholding the game-variant lookups. The API is read-only with no write operations, so the agent can never publish or edit variants regardless of how you scope it.