Answer two quick questions. We'll point you to one model to look at. Or an honest answer about what's missing.
No JavaScript? Expert request form.
Finder · no-JavaScript request
This page never submits a request for you.
Search first. A request is recorded only when a signed-in person or authorized agent chooses a request type, checks the public fields, and sends it. If nothing matches, choose one request type and check every public field before sending it.
1. Choose one request type
exact-representation- One provider, source identity, and immutable revision. A representation identifier and quantization are optional selectors.
dataset- One provider, dataset identity, and immutable revision. Configuration, split, and subset are optional selectors.
preservation- Preserve one source revision. It may remain floating unless exactness is explicitly requested, and never claims the source is runnable or complete.
runtime-verification- request a review of the available runtime evidence. Not a promise it will run.
feature- Request one named product feature. Supply or hosted-file evidence can never fulfill this kind.
2. Check the public fields
You may add commercialUse, format, hardwareTier, contextTokens, minBytes, maxBytes, and quantPreference. Locale only changes presentation. Never include names, contact details, tokens, IP addresses, user agents, referrers, locations, regions, or abuse evidence.
{
"idempotencyKey": "choose-a-stable-key-0001",
"kind": "feature",
"subject": {
"product": "hugging-bay",
"feature": "describe-the-explicit-feature"
},
"constraints": {},
"publicVisibility": "public"
}
3. Confirm, then submit once
Without JavaScript, use an authenticated HTTP client. Save the checked object as request-intent.json, keep your token in your local shell, and run:
curl --fail-with-body --request POST \
--url https://huggingbay.xyz/api/request-intents \
--header "Authorization: Bearer $HUGGING_BAY_TOKEN" \
--header "Content-Type: application/json" \
--data-binary @request-intent.json
Retry the same request with the same idempotency key and JSON. If you change the request, use a new key. A successful response includes a status URL: /request-intents/hbri_… for HTML or /api/request-intents/hbri_… for JSON.