Numenward HUB
DEVELOPER ACCESS

Publish from your agent

Create an account, then issue a revocable token for your research tools. Your agent can upload the model files you authorize it to publish. Uploading stores files; it does not start or run an agent.

Manage agent tokens

Create a model

curl https://hub.numenward.com/api/v1/models/create/ \
  -H "Authorization: Bearer $NUMENWARD_TOKEN" \
  --data-urlencode 'name=My model' \
  --data-urlencode 'slug=my-model' \
  --data-urlencode 'summary=What this model does' \
  --data-urlencode 'task=text-generation' \
  --data-urlencode 'license=Apache-2.0' \
  --data-urlencode 'card=Training, usage, evaluation and attribution' \
  --data-urlencode 'rights=true' \
  --data-urlencode 'private=true'

The response includes a release_id. Replace RELEASE_ID below with that number.

Upload and publish

curl https://hub.numenward.com/api/v1/releases/RELEASE_ID/upload/ \
  -H "Authorization: Bearer $NUMENWARD_TOKEN" \
  -F 'file=@model.safetensors'

curl -X POST https://hub.numenward.com/api/v1/releases/RELEASE_ID/publish/ \
  -H "Authorization: Bearer $NUMENWARD_TOKEN"

Upload each configuration, tokenizer and license file before publishing. Limits: 512 MiB per file and 1 GiB per account. Private models stay private when published. Change visibility through the model card editor.

Read and preserve

GET /api/v1/models lists public hosted models. Search with ?q=. Every release has a downloadable manifest and ZIP export containing the model card, files and SHA-256 checksums. Save a copy outside this service.

Storage status

Numenward currently stores uploads on its Railway volume. Filecoin with IPFS is the selected archive network. Paid replication is not active. Model pages show whether an archive CID has been recorded. A CID alone does not prove an active Filecoin storage deal.

Discovery manifest ยท Plain-text guide