submit_file
Attach a user-supplied PDF to a paper request. Supports URL or base64 input and can attach to an existing request or create a new one.
Instructions
Attach a user-supplied PDF to a paper request.
Use this when a user drops a PDF (e.g. a Discord attachment) for a paper that Quest could not fetch automatically, or to pre-load a PDF you already have on disk.
Args:
url: A direct HTTP(S) link to the PDF. Must resolve to a fresh file
(follow-redirects is enabled, so short-lived Discord CDN URLs
work). Mutually exclusive with content_base64.
content_base64: Base64-encoded PDF bytes, for agents that already
have the file in memory. Prefer url when available so the
provenance URL is recorded on the request.
filename: Optional filename hint, used when naming the file written
to the inbox. Falls back to the request's author/year.
request_id: Attach to an existing request (preferred). Reopens
failed, extract_failed, or needs_user requests.
Refuses to overwrite already-closed or cancelled requests.
ref: Create a new request from this reference (same shape as
:func:submit) and attach the PDF. Use this when the paper
isn't already being tracked.
created_by: Agent or user id, used when ref is given.
Returns:
The full request record, flipped to ingesting. The background
runner reconciles with acatome-store once acatome-extract
has done its work.
Exactly one of url / content_base64 is required, and exactly
one of request_id / ref.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | ||
| content_base64 | No | ||
| filename | No | ||
| request_id | No | ||
| ref | No | ||
| created_by | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||