com.temsor/api

Est-ce que com.temsor/api est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.temsor/api » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 43 outils

• email_verify≈ 301 tokens

  Checks an e-mail address: syntax, whether the domain can actually receive mail, disposable and role-account detection, and typo correction. No SMTP probing. Most competitors connect to the target server and try RCPT TO, which sounds thorough but produces a confident-looking number you cannot trust: most servers are catch-all, the big providers refuse to answer, and doing it in bulk gets the probing IP blacklisted. We report only what is provable — whether the domain has a mail exchanger, whether it is a known disposable service, whether the mailbox belongs to a role rather than a person, and whether the domain looks like a typo of a common one (gmial.com → gmail.com). Addresses are also normalised, so Gmail dots and +tags stop creating duplicate signups.

  Paramètres, retour & exemple (3)

  Paramètres

  • email · string · requis
    E-mail address to check.
  • rejectRoleAccounts · boolean · optionnel
  • rejectFreeProviders · boolean · optionnel

  Exemple d'appel

  {"name": "email_verify", "arguments": {"email": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• iban_validate≈ 299 tokens

  Validates an IBAN from any of 70+ countries: checksum, country length and in-country account structure, and resolves the bank and branch codes. Most free libraries stop at the mod-97 checksum. That only says the digits are self-consistent — not that the number could exist in that country. This checks the country's BBAN structure too, so a wrong-length or wrong-shaped account is rejected before your payment file reaches the bank. When only the two check digits are wrong, the correct ones are computed and returned as a suggestion, because that is what people actually mistype. Turkish, Dutch and Belgian IBANs additionally resolve to a bank name when the national code is in our table; otherwise bankName is null. This is not a SWIFT directory.

  Paramètres, retour & exemple (2)

  Paramètres

  • iban · string · requis
    IBAN, with or without spaces.
  • expectCountry · string · optionnel
    Expected country code (ISO 3166-1 alpha-2).

  Exemple d'appel

  {"name": "iban_validate", "arguments": {"iban": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• pbx_audio_chunk≈ 197 tokens

  Notify an optional audio chunk / customer URI for a live or archived call (idle $0). Prefer customer storage URI. Temsor keeps a pointer; STT only while a call is active.

  Paramètres, retour & exemple (5)

  Paramètres

  • uri · string · optionnel
    Customer-side media URI (preferred).
  • t_ms · integer · optionnel
  • pbx_id · string · optionnel
  • call_id · string · requis
  • bytes_b64 · string · optionnel
    Optional small demo chunk; production prefers URI.

  Exemple d'appel

  {"name": "pbx_audio_chunk", "arguments": {"call_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• pbx_calls≈ 119 tokens

  List recent calls with transfer path crumbs — site + customer archive browser. GET /v1/pbx/calls?limit=20. Scoped by x-temsor-pbx-key when set. Idle $0. No DID sales.

  Paramètres, retour & exemple (1)

  Paramètres

  • limit · integer · optionnel
    Max recent calls to return (1–100).

  Exemple d'appel

  {"name": "pbx_calls", "arguments": {"limit": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• pbx_calls_get≈ 119 tokens

  Get one call by id with transfer graph — customer detail drawer. GET /v1/pbx/calls/get?call_id=…. Scoped by x-temsor-pbx-key. found=false if missing. Idle $0.

  Paramètres, retour & exemple (1)

  Paramètres

  • call_id · string · requis
    Call id (e.g. call_msp_002).

  Exemple d'appel

  {"name": "pbx_calls_get", "arguments": {"call_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• pbx_calls_graph≈ 196 tokens

  Handoff graph + transfer edges — who→whom→where the promise stuck (moat). Idle $0. GET /v1/pbx/calls/graph?call_id=…&stuck_at=310. Returns path, path_tr (plain-language summary), edges, and raw transfers. Compounding asset for search/orchestration: handoff edges, not a bot transcript. Idle $0. No DID sales / no live PSTN.

  Paramètres, retour & exemple (2)

  Paramètres

  • call_id · string · requis
    Call id whose transfer graph to return.
  • stuck_at · string · optionnel
    Optional override for where the promise stuck (extension).

  Exemple d'appel

  {"name": "pbx_calls_graph", "arguments": {"call_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• pbx_dictionary≈ 247 tokens

  Managed SaaS domain dictionary (E4) — example packs thicken per pilot (tenant-scoped aliases). Boosts search + Fact extract. No invented premiums. GET /v1/pbx/dictionary?domain=hotel|pbx_provider|insurance|finance|energy|automotive|all (legacy otel|santral_firmasi|sigorta|finans|enerji|otomotiv|msp still accepted). Idle $0, no LLM. Synonyms feed archive search (match crumbs) and transcript Fact extraction. Write path: POST /v1/pbx/dictionary/add.

  Paramètres, retour & exemple (1)

  Paramètres

  • domain · string · optionnel · hotel | pbx_provider | insurance | finance | energy | automotive | otel | santral_firmasi
    Domain slice: hotel | pbx_provider | insurance | finance | energy | automotive | all (legacy keys + msp accepted)

  Exemple d'appel

  {"name": "pbx_dictionary", "arguments": {"domain": "hotel"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• pbx_dictionary_add≈ 488 tokens

  Add a synonym/alias (tenant-scoped or global demo) — E4 compounding thickens search boost + Fact extract. ≤60/hour/key → 429. Idle $0. No invented premiums. POST /v1/pbx/dictionary/add {term, alias, domain:hotel|pbx_provider|insurance|finance|energy|automotive, scope?:pbx|global}. Managed SaaS compounding (E4): tenant-scoped aliases thicken search + fact extract. No invented premiums/prices. Idle $0, no LLM. Legacy keys (otel, santral_firmasi, msp…) still accepted.

  Paramètres, retour & exemple (8)

  Paramètres

  • kind · string · optionnel · imei | tarife | oda | oda_tipi | klima | check_out | iade | sku
    Fact kind; inferred from seed term when omitted.
  • term · string · requis
    Canonical term (e.g. AC, tariff). Plain Turkish preferred.
  • alias · string · requis
    Synonym / alias to add (e.g. cooling, line package).
  • boost · number · optionnel
    Search boost weight (default 2).
  • scope · string · optionnel · pbx | global
    pbx = scoped to x-temsor-pbx-key; global = demo-wide. Default: pbx if registered key, else global.
  • domain · string · optionnel · hotel | pbx_provider | insurance | finance | energy | automotive | otel | santral_firmasi
    Domain: hotel | pbx_provider | insurance | finance | energy | automotive (legacy keys + msp accepted).
  • hint_en · string · optionnel
  • hint_tr · string · optionnel

  Exemple d'appel

  {"name": "pbx_dictionary_add", "arguments": {"term": "texte", "alias": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• pbx_events≈ 272 tokens

  Ingest call-ops events → open promises + transfer crumbs for search/orchestration. Optional HMAC. Idle $0 when no calls. Demo stores events in memory/file. Auth: omit, x-temsor-pbx-key, or x-temsor-signature = hex(HMAC-SHA256(api_key, body)); bad signature rejected when header present. BridgeEnter → transfer/handoff crumbs. Utterance/text → open Promise docs via heuristic (no LLM). Idle $0. Body ≤256 KiB → 429. Advanced: ARI/Stasis batch shape when customer runs own PBX — not Asterisk-first product copy.

  Paramètres, retour & exemple (2)

  Paramètres

  • events · array · requis
    ARI / Stasis event batch. Utterance/text fields trigger heuristic promise extract.
  • pbx_id · string · optionnel
    PBX id that emitted the ARI batch.

  Exemple d'appel

  {"name": "pbx_events", "arguments": {"events": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• pbx_facts≈ 342 tokens

  List extracted facts (IMEI, room, tariff…) from the durable index — filter by call_id, kind, domain, q. GET /v1/pbx/facts?call_id=&kind=&domain=hotel|pbx_provider|insurance|finance|energy|automotive|all&q=&limit=50. Facts come from transcript extract + domain dictionary; persist in pbx-index. Scoped by x-temsor-pbx-key. Idle $0. No DID sales. Right-to-erasure ready. Advanced: own PBX/Asterisk stays on customer.

  Paramètres, retour & exemple (5)

  Paramètres

  • q · string · optionnel
    Free-text filter over kind + value + call_id.
  • kind · string · optionnel
    Fact kind key (imei, oda, tarife, ...) or all.
  • limit · integer · optionnel
    Max facts to return (1–200).
  • domain · string · optionnel · hotel | pbx_provider | insurance | finance | energy | automotive | otel | santral_firmasi
    Domain slice: hotel | pbx_provider | insurance | finance | energy | automotive | all (legacy keys + msp accepted).
  • call_id · string · optionnel
    Filter by call id (e.g. call_msp_001).

  Exemple d'appel

  {"name": "pbx_facts", "arguments": {"q": "texte", "kind": "texte", "limit": 1, "domain": "hotel", "call_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• pbx_facts_get≈ 118 tokens

  Get one extracted fact by id — detail drawer for site + customer. GET /v1/pbx/facts/get?id=…. Scoped by x-temsor-pbx-key. found=false if missing. Idle $0. No DID sales.

  Paramètres, retour & exemple (1)

  Paramètres

  • id · string · requis
    Fact id (e.g. fact_001).

  Exemple d'appel

  {"name": "pbx_facts_get", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• pbx_index_partial≈ 377 tokens

  Upsert mid-call partial index (utterances → fact/promise hints). Path to ≤400ms whisper; ≤600/hour/key → 429; idle $0. POST /v1/pbx/index/partial {call_id, text?, speaker?, t_ms?, is_final?, live?, end_call?, promote?}. Streams partial STT queue into accumulating Fact/Promise hints while the call is live. No Temsor STT/LLM — customer posts text. Managed SaaS in-call index; no DID sales. Own PBX optional footnote. Idle $0.

  Paramètres, retour & exemple (9)

  Paramètres

  • live · boolean · optionnel
    Default true while call is live.
  • t_ms · ? · optionnel
  • text · string · optionnel
    Partial utterance / snippet (customer STT or demo). Empty = metadata-only.
  • pbx_id · string · optionnel
  • call_id · string · requis
    Live call id to upsert partial index for.
  • promote · boolean · optionnel
    Promote heuristic hints into durable Promise/Fact docs.
  • speaker · ? · optionnel
  • end_call · boolean · optionnel
    Mark live=false; idle $0 for this call.
  • is_final · boolean · optionnel
    Finalized utterance span (vs interim).

  Exemple d'appel

  {"name": "pbx_index_partial", "arguments": {"call_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• pbx_index_partial_get≈ 156 tokens

  GET mid-call partial index — accumulating facts/promises/snippets while live. GET /v1/pbx/index/partial/get?call_id=…. Returns live partial state for whisper ≤400ms path. Idle $0 when no live call. Managed SaaS in-call index; no DID sales. Own PBX optional footnote.

  Paramètres, retour & exemple (1)

  Paramètres

  • call_id · string · requis
    Call id whose live partial index to read.

  Exemple d'appel

  {"name": "pbx_index_partial_get", "arguments": {"call_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• pbx_ingest_transcript≈ 256 tokens

  Heuristic promise extractor from transcript text — creates open Promise docs (idle $0, no LLM). Detects promise-like sentences (we will, I promise, refund, cancel, call you back, tomorrow…). Optional persist_promises=false for extract without writing. Also wired via utterance text on POST /v1/pbx/events.

  Paramètres, retour & exemple (6)

  Paramètres

  • ext · string · optionnel
  • who · string · optionnel
  • pbx_id · string · optionnel
  • call_id · string · optionnel
  • transcript · string · requis
    TR utterance / transcript text to scan for promises.
  • persist_promises · boolean · optionnel
    When false, extract only (dry-run, no write). When true, create Promise docs status=open.

  Exemple d'appel

  {"name": "pbx_ingest_transcript", "arguments": {"transcript": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• pbx_persons≈ 302 tokens

  Light CRM from call graph / facts — caller phones+names and extension identities seen on transfers. GET /v1/pbx/persons?call_id=&kind=caller|extension|all&q=&limit=50. Durable Person rows from pbx-index plus derived extension identities (ext_NNN) from Transfer edges / promise.ext. Scoped by x-temsor-pbx-key. Idle $0. No DID sales. Right-to-erasure ready. Advanced: own PBX/Asterisk stays on customer.

  Paramètres, retour & exemple (5)

  Paramètres

  • q · string · optionnel
    Free-text over names, phones, org, extensions, facts.
  • kind · string · optionnel · caller | extension | all
    caller = durable Person; extension = derived from call-graph hops; all = both.
  • limit · integer · optionnel
    Max persons to return (1–200).
  • call_id · string · optionnel
    Filter persons seen on this call id.
  • include_extensions · boolean · optionnel
    Include derived extension identities (default true).

  Exemple d'appel

  {"name": "pbx_persons", "arguments": {"q": "texte", "kind": "caller", "limit": 1, "call_id": "texte", "include_extensions": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• pbx_persons_get≈ 132 tokens

  Get one light-CRM identity by id — caller Person or derived extension. GET /v1/pbx/persons/get?id=per_001|ext_101. Scoped by x-temsor-pbx-key. found=false if missing. Idle $0. No DID sales.

  Paramètres, retour & exemple (1)

  Paramètres

  • id · string · requis
    Person id (e.g. per_001) or extension id (e.g. ext_101).

  Exemple d'appel

  {"name": "pbx_persons_get", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• pbx_promises≈ 162 tokens

  List open/broken call promises for agent handoff tracking — hotel / MSP sales demo. Idle $0. GET /v1/pbx/promises?status=open returns open/unclosed promises with transfer/handoff path for orchestration. Scoped by x-temsor-pbx-key when set. Idle $0. No live PSTN.

  Paramètres, retour & exemple (1)

  Paramètres

  • status · string · optionnel · open | kept | broken | unknown | all | closed
    Promise status filter; closed = kept|broken. Sales demo uses open.

  Exemple d'appel

  {"name": "pbx_promises", "arguments": {"status": "open"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• pbx_promises_act≈ 331 tokens

  E1 moat: who→whom→promise → orchestra handoff intent (whisper/transfer/hold). Idle $0. No live PSTN. Own PBX = advanced footnote. POST /v1/pbx/promises/act {promise_id, action?}. Loads the promise + call graph, suggests whisper/transfer/hold, records orchestra intent with source_type=promise for agent handoff. Managed SaaS runtime. ≤120/hour/key (shares orchestra bucket). Idle $0. carrier/pstn always false. No cross-tenant graph merge. Advanced: not Asterisk-first glue; own PBX optional footnote.

  Paramètres, retour & exemple (6)

  Paramètres

  • action · string · optionnel · whisper | hold | transfer | pci_stop | snoop
    Default whisper. transfer uses graph stuck_at / promise.ext.
  • pbx_id · string · optionnel
  • agent_ext · string · optionnel
  • promise_id · string · requis
    Open (or any) promise id — closed loop reads call graph then records orchestra intent.
  • skip_forward · boolean · optionnel
    Default true — record intent only.
  • stasis_webhook_url · string · optionnel

  Exemple d'appel

  {"name": "pbx_promises_act", "arguments": {"promise_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• pbx_promises_close≈ 236 tokens

  Mark an open promise kept or broken with an optional privacy-safe note — makes the sales demo writable, not read-only. ≤60/hour/key → 429. POST /v1/pbx/promises/close {promise_id, status:kept|broken, note?}. Phones/emails in note are scrubbed. Scoped by x-temsor-pbx-key when set. Idle $0 — no LLM/PSTN.

  Paramètres, retour & exemple (3)

  Paramètres

  • note · string · optionnel
    Optional short operator note. Phones/emails stripped (privacy-safe).
  • status · string · requis · kept | broken
    Close outcome: kept (honoured) or broken (not kept).
  • promise_id · string · requis
    Promise id (prm_*). Sales demo marks open promises kept|broken.

  Exemple d'appel

  {"name": "pbx_promises_close", "arguments": {"status": "kept", "promise_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• pbx_promises_export≈ 189 tokens

  Export open/broken promises as CSV or JSON — hotel / PBX-provider unclosed-promise sales list. GET /v1/pbx/promises/export?status=open|closed&format=csv|json. CSV/JSON include closed_at, close_note, path crumbs. Scoped by x-temsor-pbx-key when set. Idle $0.

  Paramètres, retour & exemple (2)

  Paramètres

  • format · string · optionnel · csv | json
    Export format.
  • status · string · optionnel · open | kept | broken | unknown | all | closed
    Promise status filter; closed = kept|broken. Sales demo uses open.

  Exemple d'appel

  {"name": "pbx_promises_export", "arguments": {"format": "csv", "status": "open"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• pbx_promises_reopen≈ 156 tokens

  Undo a kept/broken close — restore an open promise so the sales demo can reverse a mis-click. ≤60/hour/key → 429. POST /v1/pbx/promises/reopen {promise_id}. Only kept|broken → open; clears closed_at/close_note. Scoped by x-temsor-pbx-key when set. Idle $0.

  Paramètres, retour & exemple (1)

  Paramètres

  • promise_id · string · requis
    Promise id (prm_*). Undo a kept|broken close — restore open.

  Exemple d'appel

  {"name": "pbx_promises_reopen", "arguments": {"promise_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• pbx_redact≈ 366 tokens

  Privacy-first erasure (default-on SaaS): clear derived index by id/phone; durable audit who/what/when + tenant scope. ≤30/hour/key → 429. Managed pointer only — not a legal deletion SLA. E.3 Privacy-first redaction for managed SaaS. mode=anonymize|delete. Lookup by target_id or phone. Clears Person/Promise/Fact/partial index + Temsor audio pointers in your tenant only (no cross-tenant). Durable audit. Raw media stays on your side. Not a legal deletion SLA. List: GET /v1/pbx/redact/audit.

  Paramètres, retour & exemple (6)

  Paramètres

  • who · string · optionnel
    Actor label for durable audit (defaults to pbx scope / demo-operator).
  • mode · string · optionnel · anonymize | delete
    anonymize (default) scrubs fields; delete removes docs.
  • phone · string · optionnel
    Caller phone — finds Person phones (+ linked derived index).
  • reason · string · optionnel
    Personal-data erasure reason.
  • target_id · string · optionnel
    Document id (prm_*, per_*, call_*, fact_*).
  • target_type · string · optionnel · promise | call | person | fact | utterance
    Index document type. Optional when `phone` is set.

  Exemple d'appel

  {"name": "pbx_redact", "arguments": {"who": "texte", "mode": "anonymize", "phone": "texte", "reason": "texte", "target_id": "texte", "target_type": "promise"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• pbx_redact_audit≈ 162 tokens

  List recent erasure actions — who/what/when + tenant scope. Managed SaaS derived-index audit; not a legal deletion SLA. GET /v1/pbx/redact/audit?limit=20. Durable audit from POST /v1/pbx/redact (E.3). Tenant-scoped. Derived index cleared; raw media not deleted by Temsor. Number→flow managed SaaS; own PBX optional. No DID sales.

  Paramètres, retour & exemple (1)

  Paramètres

  • limit · integer · optionnel
    Max recent forget actions to return (default 20).

  Exemple d'appel

  {"name": "pbx_redact_audit", "arguments": {"limit": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• pbx_register≈ 417 tokens

  Register a pilot PBX; returns pbx_id + API key once (hashed at rest). ≤5/hour/IP → 429. Idle $0. Control-plane register. API key shown once; stored hashed at rest. Send x-temsor-pbx-key to scope GET /v1/pbx/promises to this pbx_id. No speech recognition while idle.

  Paramètres, retour & exemple (8)

  Paramètres

  • name · string · optionnel
    Pilot contact name (waitlist / register).
  • email · string · optionnel
    Pilot contact email.
  • label · string · optionnel
    Human label, e.g. hotel or PBX/IT provider site.
  • pbx_id · string · optionnel
    Pilot PBX id; auto-minted if omitted.
  • webhook_url · string · optionnel
    Optional outbound webhook URL — Temsor POSTs promise/fact/orchestra/redact events.
  • webhook_events · ? · optionnel
    Event list or comma string: promise.opened|closed, fact.extracted, orchestra.act, redact, or *.
  • webhook_secret · string · optionnel
    Optional HMAC secret for outbound webhook signatures (x-temsor-signature).
  • ari_webhook_secret · string · optionnel
    ARI webhook signing secret (stored as hint only).

  Exemple d'appel

  {"name": "pbx_register", "arguments": {"name": "texte", "email": "texte", "label": "texte", "pbx_id": "texte", "webhook_url": "texte", "webhook_events": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• pbx_search≈ 290 tokens

  Agent archive search over call promises and facts — voice-Google for call-ops, not a receptionist bot. Idle $0. Demo index + domain dictionary v0. Filters: status, date, ext, competitor, stuck_after (transfer/handoff hop). Returns call-graph path + transfer edges for orchestration. Idle $0. No live PSTN.

  Paramètres, retour & exemple (7)

  Paramètres

  • q · string · optionnel
    Full-text query over promises, facts, and call summaries.
  • ext · string · optionnel
  • status · string · optionnel · open | kept | broken | unknown
  • date_to · string · optionnel
    ISO date/time upper bound.
  • date_from · string · optionnel
    ISO date/time lower bound (promise.when_iso / call.started_at).
  • competitor · string · optionnel
  • stuck_after · string · optionnel
    Filter: promise stuck after transfer to this extension (to_ext hop).

  Exemple d'appel

  {"name": "pbx_search", "arguments": {"q": "texte", "ext": "texte", "status": "open", "date_to": "texte", "date_from": "texte", "competitor": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• pbx_status≈ 123 tokens

  Control-plane status — promise/orchestra/search counts + idle $0. No DID sales. GET /v1/pbx/status. Scoped by x-temsor-pbx-key when set. Derived index on Temsor for agent search/orchestration. Idle $0. Advanced: own PBX/Asterisk stays on customer.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "pbx_status", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• pbx_webhooks≈ 358 tokens

  Register or list outbound webhooks — customer URL receives promise/fact/orchestra/redact events (HMAC if secret). POST write ≤30/hour/key → 429. POST /v1/pbx/webhooks {url, secret?, events?, ping?} registers. GET lists. ping:true sends a test delivery. Events: promise.opened, promise.closed, fact.extracted, orchestra.act, redact. Signed with x-temsor-signature when secret set. Idle $0. No DID sales. Erasure-aware. Advanced: own PBX/Asterisk stays on customer.

  Paramètres, retour & exemple (6)

  Paramètres

  • url · string · optionnel
    Outbound webhook URL (http/https). Present → register; omit on GET → list.
  • ping · boolean · optionnel
    If true with url → register then ping; if true without url → ping existing.
  • limit · integer · optionnel
    List limit (default 50).
  • events · ? · optionnel
    Events: promise.opened|closed, fact.extracted, orchestra.act, redact, or *.
  • secret · string · optionnel
    Optional HMAC-SHA256 secret → x-temsor-signature: sha256=<hex>.
  • webhook_id · string · optionnel
    For ping: target webhook id.

  Exemple d'appel

  {"name": "pbx_webhooks", "arguments": {"url": "texte", "ping": true, "limit": 1, "events": "texte", "secret": "texte", "webhook_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• pbx_webhooks_deliveries≈ 172 tokens

  List last N outbound webhook deliveries (stub or live) — promise/fact/orchestra/redact/ping. GET /v1/pbx/webhooks/deliveries?limit=20&webhook_id=. Durable log of Temsor→customer POSTs. HMAC when secret set. Idle $0. No DID sales. Erasure-aware. Advanced: own PBX/Asterisk stays on customer.

  Paramètres, retour & exemple (2)

  Paramètres

  • limit · integer · optionnel
    Max deliveries (default 20).
  • webhook_id · string · optionnel
    Filter by webhook id.

  Exemple d'appel

  {"name": "pbx_webhooks_deliveries", "arguments": {"limit": 1, "webhook_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• pbx_whisper_status≈ 166 tokens

  Capability: mode=stub|ready from TEMSOR_RTP_*. No live RTP on forge; idle $0. GET /v1/pbx/whisper/status. Reports MediaBridge config presence (TEMSOR_RTP_PATH). mode=ready means path env set — not that Asterisk RTP is flowing. live_rtp/listening always false on forge (R2–R3 IVR sidecar; R4 lab E2E harness). No ≤400ms production claim. TEMSOR_RTP_LAB=1 → optional lab_latency_ms on suggest. No DID sales.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "pbx_whisper_status", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• pbx_whisper_suggest≈ 236 tokens

  Live agent handoff cards (≤3): open promises/facts from in-call index. Idle $0. Lab: TEMSOR_RTP_LAB=1 → lab_latency_ms. POST /v1/pbx/whisper/suggest {call_id, partial_text}. Returns open promises and facts as whisper cards for agent handoff. Prefers in-call partial index when present. Mock latency_ms under 400ms (compat stub). Idle $0. No Telnyx/DID/live PSTN. Advanced: optional lab_latency_ms when TEMSOR_RTP_LAB=1 (measured; not prod SLA).

  Paramètres, retour & exemple (2)

  Paramètres

  • call_id · string · requis
    Active call id for agent UI context.
  • partial_text · string · optionnel
    Partial transcript / utterance text (no live speech recognition).

  Exemple d'appel

  {"name": "pbx_whisper_suggest", "arguments": {"call_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• phone_validate≈ 401 tokens

  Validates and normalises any phone number to E.164, with structural checks for every country calling code. For signup and checkout flows that need to store one canonical form and reject typos early. Any common input (spaces, dashes, brackets, 00 or + prefix, a stray national trunk zero) comes back as E.164 plus national notation, with the country resolved from the calling code. Numbers without an international prefix use `defaultCountry` (US when omitted), so (415) 555-0134 and +1 415 555 0134 store the same. One thing this endpoint deliberately does not claim: the current mobile operator. Numbers are portable in most markets, so a prefix says where a number was first allocated, not where it lives today. Competing APIs report the prefix owner as "the operator" and customers pick SMS routes on that basis. Where we know the original allocation we return it as `originallyAllocatedTo` with the caveat attached, because a confident wrong answer costs more than an honest gap. Countries without a full numbering plan here are validated structurally and say so in `warnings`.

  Paramètres, retour & exemple (2)

  Paramètres

  • phone · string · requis
    Phone number in any common format.
  • defaultCountry · string · optionnel
    ISO 3166-1 alpha-2 country to assume when the number has no international prefix. Defaults to US.

  Exemple d'appel

  {"name": "phone_validate", "arguments": {"phone": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• tr_address_parse≈ 234 tokens

  Splits a free-form Turkish address into neighbourhood, street, building, floor, flat, district, province and postcode. Handles the abbreviation chaos (Mah./Mh., Cd./Cad., Sk./Sok., No:12/5, K:3 D:7), cross-checks the province against the postcode, repairs misspelled district names against a dictionary, and returns a confidence score. Anything it could not place is listed in `unparsed` — nothing is dropped silently. Built for shipping, checkout and CRM systems that receive Turkish addresses typed by humans.

  Paramètres, retour & exemple (2)

  Paramètres

  • address · string · requis
    Free-text address.
  • defaultProvince · string · optionnel
    Province to assume when the address has none.

  Exemple d'appel

  {"name": "tr_address_parse", "arguments": {"address": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• tr_business_days≈ 294 tokens

  Adds business days or counts them between two dates, accounting for Turkish public and religious holidays including half-day eves. Ramadan and Sacrifice feasts follow the Hijri calendar and cannot be derived reliably by formula, so announced dates are read from a table; years without an official announcement are returned with `confirmed:false` rather than guessed silently. For delivery promises, SLA clocks, payment terms and shipping estimates.

  Paramètres, retour & exemple (4)

  Paramètres

  • end · string · optionnel
    If set, count business days between start and this date.
  • start · string · requis
    Start date (YYYY-MM-DD).
  • addDays · integer · optionnel
    Add/subtract this many business days (not calendar days).
  • countHalfDaysAsWork · boolean · optionnel
    Count Arife half-days as working days?

  Exemple d'appel

  {"name": "tr_business_days", "arguments": {"start": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• tr_iban_olustur≈ 275 tokens

  Builds a Turkish IBAN from a 5-digit bank code and account number, computing ISO 7064 check digits. A Turkish IBAN is TR + 2 check digits + 5-digit bank code + 1 reserved digit + 16-character account. This pads the account on the left, defaults the reserved digit to 0, computes the mod-97 check digits, and resolves the bank name from the same national table used by IBAN validation when the code is known. Unknown bank codes still produce a structurally valid IBAN with bankName null — existence at the bank is not claimed.

  Paramètres, retour & exemple (3)

  Paramètres

  • bankCode · string · requis
    5-digit Turkish national bank / EFT code (e.g. 00062).
  • reserved · string · optionnel
    Reserved BBAN digit after the bank code. Defaults to 0.
  • accountNumber · string · requis
    Account number, up to 16 alphanumeric characters (padded left with zeros).

  Exemple d'appel

  {"name": "tr_iban_olustur", "arguments": {"bankCode": "texte", "accountNumber": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• tr_invoice_build≈ 1538 tokens

  Builds a UBL-TR e-Invoice or e-Archive XML document from plain JSON, computing every total and validating the parties. Selling into Türkiye means issuing a UBL-TR document whose element order is fixed by schema and whose totals must agree to the kuruş, or the integrator rejects it. This endpoint takes the invoice as ordinary JSON and returns the XML. Totals you send are ignored on purpose — line amounts, per-rate VAT subtotals and the payable amount are all recomputed here, because a rounding difference of one kuruş is the most common rejection. VKN and TCKN checksums are verified, and the amount is written out in Turkish words as invoices require. It does not sign the document and does not transmit it: the financial seal and the submission to the tax authority belong to your certificate and your integrator. What comes back is a document ready to enter that step.

  Paramètres, retour & exemple (17)

  Paramètres

  • id · string · optionnel
    Invoice number. Omit and supply `series` to have it built from the series and sequence.
  • uuid · string · optionnel
    Document UUID (ETTN). Generated when omitted.
  • lines · array · requis
  • notes · array · optionnel
  • series · string · optionnel
    Three-letter series code, used with `sequence`.
  • profile · string · optionnel · TEMELFATURA | TICARIFATURA | EARSIVFATURA
    TEMELFATURA: no formal objection flow. TICARIFATURA: buyer may accept/reject. EARSIVFATURA: buyer is not an e-Invoice user.
  • currency · string · optionnel
    ISO 4217. Anything other than TRY requires `exchangeRate`.
  • customer · object · requis
  • sequence · integer · optionnel
    Sequence number within the series and year.
  • supplier · object · requis
  • issueDate · string · requis
  • issueTime · string · optionnel
  • exchangeRate · number · optionnel
    Units of TRY per one unit of `currency`.
  • amountInWords · boolean · optionnel
    Adds the payable amount written out in Turkish words as a note, the way invoices require.
  • invoiceTypeCode · string · optionnel · SATIS | IADE
  • orderReferenceId · string · optionnel
  • despatchDocumentId · string · optionnel
    Delivery note number, if the goods shipped separately.

  Exemple d'appel

  {"name": "tr_invoice_build", "arguments": {"lines": [], "customer": {}, "supplier": {}, "issueDate": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• tr_invoice_parse≈ 188 tokens

  Turns a UBL-TR e-Invoice or e-Archive XML document into clean JSON: parties, line items, taxes and totals. Works regardless of the namespace prefix the sender used (cbc:, cac:, ns0:), normalises single-line documents into arrays, and reports amount mismatches in `warnings` instead of returning quietly wrong totals. The job that costs accounting and expense software the most engineering time.

  Paramètres, retour & exemple (1)

  Paramètres

  • xml · string · requis
    UBL-TR e-Invoice / e-Archive (e-Arsiv) XML body.

  Exemple d'appel

  {"name": "tr_invoice_parse", "arguments": {"xml": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• tr_labor≈ 520 tokens

  Computes Turkish severance (kıdem), notice (ihbar) and annual-leave entitlement from service dates and the gross wage, using the official ceiling and minimum-wage tables for the given day. Payroll and HR tools in Turkey chase a parameter that changes every January and July: the severance ceiling, the SGK cap, the minimum wage. This endpoint applies the statutory formulae (Labour Law 4857 arts. 17 and 53, former 1475 art. 14) to those tables. The ceiling is applied to the monthly wage, not the total. Stamp tax (0.759%) is deducted from severance; income tax is not — kıdem is exempt. Notice pay IS taxable; we return the gross and say so, because the actual withholding depends on the employee's cumulative tax base. What this will not tell you: whether the employee is entitled to severance at all. That depends on the reason for termination (retirement, just cause, marriage, military service…). Treating the number as "what is owed" is how you lose at trial.

  Paramètres, retour & exemple (6)

  Paramètres

  • age · integer · optionnel
    Employee age at termination — affects annual-leave entitlement (under 18 or 50+).
  • asOf · string · optionnel
    Rate table date. Defaults to endDate.
  • endDate · string · requis
    Termination date (YYYY-MM-DD). Inclusive of this day.
  • startDate · string · requis
    Employment start date (YYYY-MM-DD).
  • monthlyGross · number · requis
    Gross monthly wage the severance is based on (giydirilmiş brüt).
  • unusedLeaveDays · number · optionnel
    Unused annual-leave days, if you also want the unused-leave gross.

  Exemple d'appel

  {"name": "tr_labor", "arguments": {"endDate": "texte", "startDate": "texte", "monthlyGross": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• tr_money_to_words≈ 255 tokens

  Writes a monetary amount out in Turkish words, the way invoices, cheques and promissory notes require. Applies the rules that trip up generic libraries: Turkish says "bin", never "bir bin"; the kuruş part is read separately; and both "1.234,56" and "1,234.56" are accepted and told apart automatically. A mandatory field on Turkish e-invoices, cheques and notes — with no off-the-shelf API until now.

  Paramètres, retour & exemple (4)

  Paramètres

  • style · string · optionnel · lower | title | upper
    Output letter case.
  • amount · ? · requis
    Amount. Accepts both "1.234,56" and 1234.56.
  • currency · string · optionnel · TRY | USD | EUR | GBP
  • wrapHash · boolean · optionnel

  Exemple d'appel

  {"name": "tr_money_to_words", "arguments": {"amount": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• tr_posta_kodu≈ 205 tokens

  Validates a 5-digit Turkish postal code and resolves the province from the first two digits (plate map). PTT postal codes are five digits; the leading pair matches the province plate code for the 81 provinces. This endpoint checks the shape, maps 01–81 to the province name, and returns null with confidence none when the prefix is outside that range — it does not invent a district. District-level resolution needs the full PTT directory and is out of scope here.

  Paramètres, retour & exemple (1)

  Paramètres

  • postalCode · string · requis
    Turkish 5-digit postal code, with or without spaces.

  Exemple d'appel

  {"name": "tr_posta_kodu", "arguments": {"postalCode": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• tr_qr_odeme≈ 369 tokens

  Builds a person-to-person TR Karekod (FAST) payment payload from IBAN, name and optional TRY amount. Text only — no PNG. Turkish instant payments (FAST) can start from a TR Karekod that encodes the payee IBAN and name in EMV-style TLV. This builds the person-to-person organisation (payload format indicator 750210): application template with IBAN, payee name, optional 12-digit kuruş amount, optional free-text explanation, and a CRC-16/CCITT-FALSE trailer. The Turkish IBAN is normalised and checked with ISO 7064 mod-97; non-TR IBANs and non-TRY currencies are rejected. This does not send money and does not render a QR image.

  Paramètres, retour & exemple (6)

  Paramètres

  • iban · string · requis
    Beneficiary Turkish IBAN (with or without spaces).
  • name · string · requis
    Payee name shown to the payer (2–26 chars after trim).
  • amount · number · optionnel
    TRY amount; omitted → static QR (payer enters amount).
  • currency · string · optionnel
    Must be TRY if provided.
  • explanation · string · optionnel
    Optional remittance note (application free field 10).
  • generatorCode · string · optionnel
    QR generator / EFT code (4 digits). Defaults to last 4 of the IBAN bank code.

  Exemple d'appel

  {"name": "tr_qr_odeme", "arguments": {"iban": "texte", "name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• tr_tebligat_clock≈ 796 tokens

  Computes the deemed-received date and the HMK deadline (with holiday shifting) for a Turkish notification, from the date the underlying event actually happened. Turkish notification law (7201) ties the deadline clock to an event that is not "the date on the letter" — for electronic notification the UETS platform reports send, read AND reached dates, and only the reached date starts the clock (art. 7/a: deemed received 5 calendar days after reaching the address, whether or not it was opened). HMK adds two more rules on top: the day of notification itself does not count (art. 92 — the period starts the next day) and if the computed last day lands on a weekend or a full public/religious holiday, it moves to the next business day (art. 93); a half-day eve (arife) does not shift it. What this will not tell you: whether the notification was itself valid, or what a specific `periodType` (itiraz, temyiz, cevap…) is in days for your case — that number differs by statute and we do not guess it; supply `periodDays` yourself. Only the "hmk" law family is covered so far.

  Paramètres, retour & exemple (8)

  Paramètres

  • type · string · requis · electronic | physical | vekil | ilanen | last_known_address
    Notification method. Determines which event `basisDate` refers to and whether the deemed-received date is same-day or shifted.
  • basisDate · string · requis
    The date `basisLabel` describes for this type — for "electronic" this is the date UETS reports the message as reached, not sent or read.
  • lawFamily · string · requis · hmk
    Body of procedural law the period is computed under. Only "hmk" (Code of Civil Procedure) is supported so far.
  • periodDays · integer · requis
    Length of the statutory or judicial period, in days, counted from `periodStart`.
  • periodType · string · optionnel
    Free-text label for the period (e.g. "itiraz", "temyiz"), echoed back only — not mapped to a day count.
  • hasAttorney · boolean · optionnel
    Whether the addressee has a registered attorney of record. When true and `type` is not "vekil", a TK 11 warning is added noting that service should have gone to the attorney.
  • ilanenDeemedDays · integer · optionnel
    Only valid with type "ilanen": number of days the competent authority set for the notice to become deemed received (TK 31), 7-15, default 7. Not the number of days for the underlying period.
  • subjectToJudicialRecess · boolean · optionnel
    Whether this matter is subject to the judicial recess (adli tatil, HMK 104) instead of being exempt. Only affects the result when `lawFamily` is "hmk" and the computed last day falls in the 20 July - 31 August window.

  Exemple d'appel

  {"name": "tr_tebligat_clock", "arguments": {"type": "electronic", "basisDate": "texte", "lawFamily": "hmk", "periodDays": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• tr_validate≈ 237 tokens

  Validates Turkish national ID, tax number, IBAN, licence plate, IMEI, barcodes, KEP, MERSİS, postal code and ISBN from one endpoint, with type auto-detection. Goes past a yes/no: resolves the bank behind an IBAN, the province behind a licence plate and the GS1 country prefix behind a barcode. Pure local computation — no upstream service is called, so latency is microseconds and the answer never changes for the same input.

  Paramètres, retour & exemple (2)

  Paramètres

  • type · string · optionnel · auto | tckn | vkn | iban | plate | imei | gtin | kep
    Omitted → inferred from the format.
  • value · string · requis
    Value to validate.

  Exemple d'appel

  {"name": "tr_validate", "arguments": {"value": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• tr_vat≈ 410 tokens

  Splits a Turkish amount into net, VAT and (optionally) withholding: who pays the seller, who remits the withheld VAT. For invoice lines and checkout totals that have to show KDV dahil / hariç and, when the parties are in a withholding (tevkifat) situation, the split between what the buyer pays the seller and what the buyer remits to the tax office. Rates are 0, 1, 10 and 20 percent. Withholding is a fraction of the VAT (2/10 through 10/10), or a named code from the GİB partial-withholding list. The 2026 threshold (TRY 12,000 gross) is reported and compared with the amount, but `applies` is always null: whether withholding actually applies depends on the taxpayer status of both parties, which this endpoint does not know. Feeding it a fraction is not a legal opinion.

  Paramètres, retour & exemple (4)

  Paramètres

  • rate · ? · optionnel
    VAT rate in percent. 0, 1, 10 or 20.
  • amount · number · requis
    The amount to tax. See amountIncludesVat.
  • withholding · string · optionnel
    Withholding fraction such as "5/10", or a code from the list (reklam, tasima, hurda, isgucu…).
  • amountIncludesVat · boolean · optionnel
    If true, `amount` is the gross (KDV dahil); if false, it is the net/matrah.

  Exemple d'appel

  {"name": "tr_vat", "arguments": {"amount": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://api.temsor.com/mcp