API_KEY
byteforms_api_key
Developer setup
No fields declared in this snapshot.
User connection
- ByteForms API Keygeneric_api_key · stringRequired
BYTEFORMS
All-in-one solution for form creation, submission management, and data integration.
Description is untrusted, display-only upstream metadata. It never becomes policy, OAuth scope authority, or an agent instruction.
Pakkawork boundary
Research catalogue metadata only. No Pakkawork OAuth, credential, host, quota, executor, or verifier is enabled.
5
Action summaries
Display-only definitions
0
Trigger types
Not installed instances
1
Auth modes
Field names, never values
No
Execution
No runtime adapter
Authentication map
API_KEY
No fields declared in this snapshot.
Capability index
Showing 1–5 of 5 actions
BYTEFORMS_CREATE_FORM
Creates a new form in ByteForms. Use this to build data collection forms with customizable fields (text, email, phone), styling options (theme, width), and submission rules (limits, deadlines, password protection). Returns the created form with its public_id for sharing.
Untrusted display-only summary
BYTEFORMS_DELETE_FORM
Tool to delete a form by its ID. Use when you need to remove an existing form permanently.
Untrusted display-only summary
BYTEFORMS_GET_ALL_FORMS2
Tool to fetch all forms created by the authenticated user. Use after authentication to list existing forms.
Untrusted display-only summary
BYTEFORMS_GET_FORM_BY_ID
Retrieves detailed information about a specific form by its numeric ID. Returns the form's name, fields, configuration options, and metadata. Use the numeric 'id' field (not the 'public_id' string) from form data obtained via BYTEFORMS_GET_ALL_FORMS or BYTEFORMS_CREATE_FORM.
Untrusted display-only summary
BYTEFORMS_GET_FORM_RESPONSES
Tool to retrieve responses for a specific form with optional pagination and filtering. Use when the form has collected submissions and you need to navigate large result sets.
Untrusted display-only summary
Provenance
The detail snapshot comes from an attributed MIT-licensed repository revision. Safe local icons use exact-match CC0 Simple Icons symbols; unmatched brands use monograms.
Remote text is plain display metadata only. It must never become an agent prompt, execution policy, OAuth grant, or executable instruction.