{"name":"Stratigos Security page finder","kind":"page-finder","description":"Ask in the reader's own words and get the one page on stratigossecurity.com most likely to answer, with the short answer and its sources where the site has them, and up to three other questions to ask instead, scored by word matching against an index of what each page answers, not by a model. The question alone gets the general answer. Include who it is for and what changes it, and you get the specific one: the role gets the version written for that reader; the kind of organization gets the answer for who has to act; the situation (device type, pathway, stage, the decision at hand) gets the page for that case. Each detail narrows the result and the reply says which it used; one call with them beats two without. Kinds and situations only, never names. What is sent is kept with the ordinary request log so the site can be improved around what visitors come for; secondarily, the optional model and developer fields are compared with the request headers for a small research project on how agents read the web. Nothing here runs code, fetches other resources, or asks anything that identifies the person you work for.","documentation":"https://stratigossecurity.com/agents/?via=api","session":"1f924700-28b7-42f3-8418-83717faf05f3","via":null,"actions":[{"id":"find-pages","method":"GET","url":"https://stratigossecurity.com/api/agent/find","example":"https://stratigossecurity.com/api/agent/find?q=what%20FDA%20reviewers%20expect%20in%20the%20cybersecurity%20section%20of%20a%20510(k)&role=regulatory","path_form":"https://stratigossecurity.com/api/agent/find/{question}","path_form_example":"https://stratigossecurity.com/api/agent/find/what%20FDA%20reviewers%20expect%20in%20the%20cybersecurity%20section%20of%20a%20510(k)","post_form":"POST the same fields as JSON or a form body to /api/agent/find. Preferred for detailed project descriptions: a GET query appears in the URL and in whatever logs sit between you and this site.","parameters":{"q":"string. The reader's question, in their own words, up to 1000 characters. Full questions match better than keywords, because pages are matched against the ways people actually ask. The question alone gets the general answer; role, organization, and situation get the specific one, and the reply lists which of them it used. Required unless the call is a next step on an earlier query.","role":"string. Who the answer is for. Include it: pages name the readers they were written for, and the role moves those pages to the top, so a regulatory lead gets submission wording and an engineer gets design and testing detail instead of the general page. One of regulatory, engineering, quality, clinical, executive, security, research, press; or a few words of your own if none fits (they are kept as given).","organization":"string. The reader's kind of organization. Include it: the same question has different answers for a device maker, a hospital, and a consultancy, and this picks the one for your reader. One of device-maker, hospital-or-health-system, consultancy-or-law-firm, regulator-or-notified-body, investor-or-acquirer, academic; or a few words of your own if none fits. A kind, never a name.","situation":"string, up to 300 characters. What changes the answer: device type, submission pathway (510(k), PMA, De Novo), stage (before submission, under review, on the market), the decision at hand. Include it: these words join the matching, so \"Bluetooth insulin pump, 510(k) under review\" finds the wireless and review pages the bare question misses, and the reply names the words it used. Describe the situation, not the person: no names, companies, or contact details.","next":"string, on a later call with the same session, or as the path /api/agent/find/found/<session>/<step>. One of full, more, refine, new: full returns the whole entry (the answer, what we have seen, our view), its sources, the service it leads to, related questions to ask, and the page and JSON addresses; more returns the next two or three questions that come close, each with an address that asks it; refine returns the finder with your words pre-filled to edit, and what sharpens a match; new returns a clean finder address for the next question.","model":"string, optional. Model name and version. Compared with the request headers.","developer":"string, optional. The organization that trained the model.","harness":"string, optional. The product or harness you run inside.","task_category":"string, optional. One of: answering-question, research-company, indexing, testing, security, sales-marketing, browsing, other; or a few words of your own.","discovery":"string, optional. How you found this. One of: llms-txt, robots-txt, link-rel, link-header, footer, openapi, api, search, person, other; or a few words of your own."},"response":"JSON: answer (the one best match: for a Q&A entry its title, url, short_answer, status, reviewed date, sources, leads_to (the service page it points to), and json_url (the entry as JSON); for an ordinary page its title, url, and summary), other_questions (up to three, each with an ask_url that asks the finder that question), matched, sharpen (what to add for a closer match, with a ready-made address), notes (what the site does not publish, when the question asked), next_step (links that each say what they return), and session. When nothing on the site answers closely: answer null, a message saying so and what the site covers, and only the refine and new steps."},{"id":"introduce-yourself","method":"POST","url":"https://stratigossecurity.com/api/agent/report","optional":true,"content_types":["application/json","application/x-www-form-urlencoded"],"fields":{"model":"string, required. Model name and version.","developer":"string, required. The organization that trained the model.","harness":"string, optional. The product or harness you run inside.","task_category":"string, required. One of: answering-question, research-company, indexing, testing, security, sales-marketing, browsing, other.","discovery":"string, required. How you found this. One of: llms-txt, robots-txt, link-rel, link-header, footer, openapi, api, search, person, other.","goal":"string, optional. What the reader is trying to accomplish, in general terms. Used to choose suggested_reading.","audience":"string, optional. Who the reader is, in general terms: a role and kind of organization. No names, employers, or contact details.","wanted":"string, optional. What information would have helped most, or what you looked for and did not find.","outcome":"string, optional. Did you find what you needed? One of: yes, partly, no, not-looking, other.","notes":"string, optional. Nothing that identifies a person.","session":"string, optional. Include \"1f924700-28b7-42f3-8418-83717faf05f3\" so the submission joins the request that fetched this description."},"response":"JSON receipt with what was recorded, what the request itself indicated, whether the two agree, and suggested_reading for the goal."}],"do_not_include":"Anything that identifies a person or organization: names, employers, email addresses, phone numbers, credentials, or quoted prompts.","what_we_record":"https://stratigossecurity.com/agents/#what-we-record","contact":"https://stratigossecurity.com/contact/?via=agents-page","other_formats":["https://stratigossecurity.com/api/agent/openapi.json","https://stratigossecurity.com/llms.txt","https://stratigossecurity.com/site-index.json"]}