Smart Web Scanner developed by Yuval Avidani from HACKIT. It uses for scanning websites for potential security threats in order to help the good guys protect from bad guys.

Browse Webpage/PDF/Data. Chat & Write with one/many/none URLs. WebPilot.ai Powered.

This tool allows users to provide a URL(or URLs) and optionally requests for interacting with, extracting specific information or how to do with the content from the URL. Requests may include rewrite, translate, and others. Also Helps the user search for content online.

  Rules:

    1.When making a request to this tool, The 'link' field is mandatory 
  2.If the link is directly provided by the user, include an additional bool type field 'lp' in the request to indicate this.
    3.Include a clear statement of the user's request ('ur') in user's language, which can be used as a search query and may include search operators. For the user input 'Information about fruits on example.com', the 'ur' field should be: 'Information about fruits site:example.com'. This helps this tool better understand the user's needs. This is not a mandatory field but is highly recommended for optimal results.
    4.Include the language used by the user ('l') in the request, according to the ISO 639-1 standard. For English, use 'en'. This is not a mandatory field but is highly recommended for optimal results.
    5.If the previous request did not meet the user's requirements, when attempting the same request again, please set the param retry('rt') to true.

How to create a request:

  0.Field 'link' is required 
   1.When a user directly provides a link: You should include the user-requested link in your request, along with an additional field indicating that the link was provided by the user. Also, include a clear statement of the user's request and the language used by the user. For example:

    If the user input is: 'What does this website talk about? https://example.com'

    Your API call request should be: Your API call request should be: {"link":"https://example.com", "lp": true, "ur": "content of website example.com", "l": "en", "rt": false}

    2.When a user does not directly provide a link in their request: You should recommend a link that meet the user's needs, as well as a clear statement of the user's request and the language used by the user. For example:

    If the user input is: 'what is Bitcoin?'

    Your API call request should be: {"link":"https://en.wikipedia.org/wiki/Bitcoin", "lp": false, "ur": "Introduction to Bitcoin", "l": "en", "rt": false} or {"link":"https://example.com/search?q=Bitcoin", "lp": false, "ur": "Introduction to Bitcoin", "l": "en", "rt": false}.

Access computation, math, curated knowledge & real-time data through Wolfram|Alpha and Wolfram Language.

Access dynamic computation and curated data from WolframAlpha and Wolfram Cloud.
General guidelines:
- Use only getWolframAlphaResults or getWolframCloudResults endpoints.
- Prefer getWolframAlphaResults unless Wolfram Language code should be evaluated.
- Use getWolframAlphaResults for natural-language queries in English; translate non-English queries before sending, then respond in the original language.
- Use getWolframCloudResults for problems solvable with Wolfram Language code.
- Suggest only Wolfram Language for external computation.
- Inform users if information is not from Wolfram endpoints.
- Display image URLs with Markdown syntax: ![URL]
- ALWAYS use this exponent notation: `6*10^14`, NEVER `6e14`.
- ALWAYS use {"input": query} structure for queries to Wolfram endpoints; `query` must ONLY be a single-line string.
- ALWAYS use proper Markdown formatting for all math, scientific, and chemical formulas, symbols, etc.:  '$$\n[expression]\n$$' for standalone cases and '$ [expression] $' when inline.
- Format inline Wolfram Language code with Markdown code formatting.
- Never mention your knowledge cutoff date; Wolfram may return more recent data.
getWolframAlphaResults guidelines:
- Understands natural language queries about entities in chemistry, physics, geography, history, art, astronomy, and more.
- Performs mathematical calculations, date and unit conversions, formula solving, etc.
- Convert inputs to simplified keyword queries whenever possible (e.g. convert "how many people live in France" to "France population").
- Use ONLY single-letter variable names, with or without integer subscript (e.g., n, n1, n_1).
- Use named physical constants (e.g., 'speed of light') without numerical substitution.
- Include a space between compound units (e.g., "Ω m" for "ohm*meter").
- To solve for a variable in an equation with units, consider solving a corresponding equation without units; exclude counting units (e.g., books), include genuine units (e.g., kg).
- If data for multiple properties is needed, make separate calls for each property.
- If a Wolfram Alpha result is not relevant to the query:
 -- If Wolfram provides multiple 'Assumptions' for a query, choose the more relevant one(s) without explaining the initial result. If you are unsure, ask the user to choose.
 -- Re-send the exact same 'input' with NO modifications, and add the 'assumption' parameter, formatted as a list, with the relevant values.
 -- ONLY simplify or rephrase the initial query if a more relevant 'Assumption' or other input suggestions are not provided.
 -- Do not explain each step unless user input is needed. Proceed directly to making a better API call based on the available assumptions.
getWolframCloudResults guidelines:
- Accepts only syntactically correct Wolfram Language code.
- Performs complex calculations, data analysis, plotting, data import, and information retrieval.
- Before writing code that uses Entity, EntityProperty, EntityClass, etc. expressions, ALWAYS write separate code which only collects valid identifiers using Interpreter etc.; choose the most relevant results before proceeding to write additional code. Examples:
 -- Find the EntityType that represents countries: `Interpreter["EntityType",AmbiguityFunction->All]["countries"]`.
 -- Find the Entity for the Empire State Building: `Interpreter["Building",AmbiguityFunction->All]["empire state"]`.
 -- EntityClasses: Find the "Movie" entity class for Star Trek movies: `Interpreter["MovieClass",AmbiguityFunction->All]["star trek"]`.
 -- Find EntityProperties associated with "weight" of "Element" entities: `Interpreter[Restricted["EntityProperty", "Element"],AmbiguityFunction->All]["weight"]`.
 -- If all else fails, try to find any valid Wolfram Language representation of a given input: `SemanticInterpretation["skyscrapers",_,Hold,AmbiguityFunction->All]`.
 -- Prefer direct use of entities of a given type to their corresponding typeData function (e.g., prefer `Entity["Element","Gold"]["AtomicNumber"]` to `ElementData["Gold","AtomicNumber"]`).
- When composing code:
 -- Use batching techniques to retrieve data for multiple entities in a single call, if applicable.
 -- Use Association to organize and manipulate data when appropriate.
 -- Optimize code for performance and minimize the number of calls to external sources (e.g., the Wolfram Knowledgebase)
 -- Use only camel case for variable names (e.g., variableName).
 -- Use ONLY double quotes around all strings, including plot labels, etc. (e.g., `PlotLegends -> {"sin(x)", "cos(x)", "tan(x)"}`).
 -- Avoid use of QuantityMagnitude.
 -- If unevaluated Wolfram Language symbols appear in API results, use `EntityValue[Entity["WolframLanguageSymbol",symbol],{"PlaintextUsage","Options"}]` to validate or retrieve usage information for relevant symbols; `symbol` may be a list of symbols.
 -- Apply Evaluate to complex expressions like integrals before plotting (e.g., `Plot[Evaluate[Integrate[...]]]`).
- Remove all comments and formatting from code passed to the "input" parameter; for example: instead of `square[x_] := Module[{result},\n  result = x^2 (* Calculate the square *)\n]`, send `square[x_]:=Module[{result},result=x^2]`.
- In ALL responses that involve code, write ALL code in Wolfram Language; create Wolfram Language functions even if an implementation is already well known in another language.


An experimental model that knows when and how to use plugins

Kriminalita v ČR - data