Skip to main content
Use registry__request_file_upload before creating an artifact whose bytes cannot fit in a tool argument. Registry serves this tool. Earlier releases listed it as extension__file__request_upload, a name the gateway no longer serves.
  • Optional inputs: size_bytes, session_id, and Gateway’s rationale.
  • Returns: upload_url, upload_key, is_presigned, expires_in_seconds, and max_bytes.
  • Effect: write; mints a temporary upload capability.
If is_presigned is true, send the bytes without the Gateway bearer token. If it is false, resolve the root-relative URL against the Gateway origin and send the bearer token. Treat the URL as a password and do not log it. After the upload, create the artifact with upload_key in its metadata. The artifact kind’s other required fields still apply. Creating the artifact is refused with 422 validation_failed when the uploaded bytes contradict the media_type it declares — markup or an executable declared as an image, for example. Declare the media type the bytes actually are, or upload the bytes you meant to send, then create the artifact again.