⚡ Skills admin

← ChatChats admin

Switches

ⓘ
Everything starts off. Turn on Skills first (reads only), then Write actions, Scheduler, Notifications and Agent API when you're ready. Each switch takes effect immediately β€” no redeploy.

Skills

➕ Add a skill
Paste a skill definition (JSON). URLs must be https (or http:// to a private 10.x address with the Private network switch on). An id may go in the URL path as {{args.id}}; other values go in query or body using {{args.x}}, keys with {{secret.name}}, the confirmation id with {{request.id}}. Filters: |csv, |html, |isodate, |daystart. Params can use "format": "phone".

🧠 Memory

ⓘ How it works
Learning after each answer uses the chat's own model. Inbox items, project briefs and the nightly tidy (merge duplicates, refresh briefs, close old to-dos, suggest projects) use the background model below β€” in-cluster, no API key. Agents: POST api/skills/v1/memory/ask {"question":"…"}, …/memory/remember {"text":"…","about":"…"}, MCP tools memory__ask / memory__remember; phone agent tool caller_context. Work agents read Work projects only; Personal agents also read Private ones; Separate projects and health/money notes are never shared.

Automations

Access tokens

ⓘ How to connect
Other agents call skills with a token: GET api/skills/v1, POST api/skills/v1/<skill>/<action> with {"args":{…}}, or MCP at api/mcp. Header: Authorization: Bearer sk_swift_…. Needs the Agent API switch.

πŸ“ž Phone assistant

ⓘ How it works
SwiftSIP forwards the voice agent's tool calls here: POST api/agent-tools/v1/<tool> (in-cluster: http://<voicechat ClusterIP>:8080/api/agent-tools/v1/<tool>) with a Phone agent tools token from Agent access. Tools: check_availability (free times only β€” never titles, people or links) and take_message (β†’ πŸ“₯ Inbox + notification). Needs the Agent API switch.
Meetings you declined (matched on these emails) count as free; all-day events block the day; times already past are never offered.

πŸ“ž Phone numbers

ⓘ How it works
SwiftSIP posts call.ended (and optionally call.ringing) to http://<voicechat ClusterIP>:8080/api/skills/v1/events with a Call events token (Agent access) and an HMAC signature using the secret shown when that token is created. Each call lands in the owner's πŸ“₯ Inbox with a πŸ“ž Call back button. Needs the Agent API switch.
Number β†’ user. * = any other number. Without a match, outbound calls go to whoever requested them, everything else to the first admin.

πŸ“ž Call routing & approval

ⓘ How it works
Routing (incoming): SwiftSIP posts each call to http://<voicechat ClusterIP>:8080/api/skills/v1/route; Swift Chat answers from the Phone numbers table (βš™ per number) within a few ms. Blocked callers are refused (busy). Approval (outgoing): SwiftSIP posts to …/api/skills/v1/authorize before dialing; Swift Chat checks the user, the number and the limits below using its own call usage records. Create a Call routing and a Call approval token under Access tokens (token + HMAC secret each) for SwiftSIP's route and preCallAuth settings. Turn the matching switch on before SwiftSIP enables its side.
Incoming Β· blocked callers (one per line)
Outgoing Β· allowed prefixes
0 = no limit. +1 900 / 976 numbers are always refused.
Test
⚡ Instant call results

πŸ’² Plans

ⓘ How it works
SwiftSIP prices every call with the rate of the tier Swift Chat sends (plan id = SwiftSIP tier name). Swift Chat tracks each user's spend this month from the usage records and applies their allowance: outbound calls are checked by Call approval, incoming calls get their length capped (or are refused) by Call routing. Allowance 0 = no limit. Rates here are shown to users; keep them in step with SwiftSIP's tier rates.
Users Β· plan and custom allowance (blank = the plan's)

πŸ“ž Call usage

ⓘ How it works
SwiftSIP posts one call.usage record per call to http://<voicechat ClusterIP>:8080/api/skills/v1/usage (in-cluster), signed like call events. Create a Call usage token under Access tokens and put the token + HMAC secret in SwiftSIP's billing.usageWebhook. Records are matched to users by tenant id (when it's an email), the chat that placed the call, or the Call alerts number table. Months are UTC. Costs come from SwiftSIP; Swift Chat never recalculates them.
Calls this month

Activity log