Connected systems and incoming messages
Your backend can call any service with an API, and take the messages those services send back. You paste each key in the cockpit, and Typestate stores it encrypted with AES-256-GCM.
How Typestate does it
- Your agent describes the service: its address, how it signs in, and what your backend asks of it.
- You paste the key on a page of the cockpit. Your agent never sees it.
- When a service sends a message in, Typestate checks its signature before any action runs. A message that arrives twice runs once.
What you can do with it
- Charge a card with Stripe and hear when the payment clears.
- Post to a Slack channel when an order comes in.
- Send a call after the record is saved, and try again if it fails.
- See each call that went out, and send a failed one again.
What Typestate gives you
- Services
- any with an HTTP API; 25 ready in the catalog
- Sign in to the service
- API key, basic, bearer, OAuth2 client, JWT
- Incoming proof
- HMAC, shared secret, ed25519 or RS256 signature
- Keys
- encrypted with AES-256-GCM, never shown to your agent
- Call history
- 14 days, or 1 to 90
Say this to your agent
Connect Stripe. When a payment succeeds, mark the order paid.