[Feature Request]: AffixIO host attestation for agent-triggered messaging and account actions

Open Beginner friendly
#1,214 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
62/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
node.js, typescript
Domain
documentation

Research direction

No specific file is named; start by checking the README and existing examples for guidance on making message, call, and account API requests. Add a short AffixIO host-attestation example or README pointer, keeping Twilio authentication unchanged. Done means the documentation shows attestation before the relevant client calls without suggesting a full SDK middleware wrapper.

Written by the indexing model from the issue text.

Description

Preflight Checklist
  • I have read the Contributing Guidelines for this project.
  • I agree to follow the Code of Conduct that this project adheres to.
  • I have searched the issue tracker for a feature request that matches the one I want to file, without success.
  • This is not a general Twilio feature request or bug report. It is a feature request for the twilio-node JavaScript package.
Problem Description

Agent and automation stacks use twilio-node to send SMS/voice, buy numbers, and change account resources. Account credentials authorize the API. They do not prove that a specific host-side tool step was approved and completed before the message or account mutation fires.

AffixIO proves a host-side ACTION completed (signed yes/no). PII stays on the host. Not person/age/KYC.

npm i affixio
# optional local MCP
npm i @affixio/[email protected]
Proposed Solution

Add a short docs or examples note for gating agent-triggered Twilio actions with AffixIO on the host before twilio-node calls run. Sit:

  1. Agent intends to send a message, start a call, or mutate account resources.
  2. AffixIO attests that privileged host action (signed yes/no).
  3. Only then call client.messages.create / calls / account APIs.
  4. Keep Twilio auth as-is; AffixIO is attestation beside it, not a replacement.

Not asking for a full SDK middleware wrap. A community example under examples/ or a README pointer is enough. We can PR a tiny example if you want that shape.

Alternatives Considered
  • App-level logging only: easy to skip under agent loops.
  • Twilio Authy / Verify: different problem (end-user verification), not host-side tool attestation.
  • Custom wrappers around every call: works, but teams rebuild the same gate; a documented AffixIO pattern avoids that.
Additional Information

Happy to keep this issue-only, or open a minimal examples PR if that is preferred.

Dominant language
TypeScript
Stars
1.5k
Forks
568
Avg merge
12h 52m
Merged PRs (30d)
7

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from twilio/twilio-node

All issues in twilio/twilio-node

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.