{
  "title": "Byte order mark editor",
  "human_url": "https://happytails.ai/en/developer-tools/byte-order-mark-editor/",
  "agent_url": "https://happytails.ai/agents/en/developer-tools/byte-order-mark-editor/",
  "language": "en",
  "markdown_url": "https://happytails.ai/en/developer-tools/byte-order-mark-editor.md",
  "content": "Byte order mark editor\nInspect, add or remove a UTF byte order mark without changing the encoded payload.\nHow can we improve this tool?\nReport a problem or share an idea.\nPlease leave out private information. Your message and the tool name go to our team via PostHog.\nHow to use Byte order mark editor\nChoose the local file or files.\nReview the action and limits, then run the inspection.\nCheck the result and download a separate output or report.\nUseful next steps\nLine ending auditor\nBinary file comparator\nFile hash\nInspect the leading bytes\nChoose a local file and inspect the detected marker. A missing marker does not identify the file encoding.\nAdd or remove explicitly\nChoose the action. Adding validates the payload against the selected encoding; conflicting markers and invalid code units are rejected.\nKeep the original\nDownload a new binary file. Every byte after the marker is preserved, and the source is never modified.",
  "content_format": "text/plain",
  "visibility": "public",
  "links": [
    {
      "name": "Line ending auditor",
      "url": "https://happytails.ai/en/developer-tools/line-ending-auditor/"
    },
    {
      "name": "Binary file comparator",
      "url": "https://happytails.ai/en/developer-tools/binary-file-comparator/"
    },
    {
      "name": "File hash",
      "url": "https://happytails.ai/en/developer-tools/file-hash/"
    }
  ],
  "tool": {
    "id": "byte-order-mark-editor",
    "category": "developer-tools",
    "built": true,
    "requirements": "One file up to 256 MiB. Adding a marker validates the selected UTF-8, UTF-16 or UTF-32 encoding. Removing a marker strips only a recognized leading marker. No encoding conversion is performed.",
    "implementation": {
      "fields": [
        {
          "key": "action",
          "label": "Action",
          "value": "Inspect",
          "type": "select",
          "values": [
            "Inspect",
            "Add marker",
            "Remove marker"
          ]
        },
        {
          "key": "encoding",
          "label": "Encoding to validate when adding",
          "value": "UTF-8",
          "type": "select",
          "values": [
            "UTF-8",
            "UTF-16LE",
            "UTF-16BE",
            "UTF-32LE",
            "UTF-32BE"
          ]
        }
      ],
      "files": true,
      "input": false,
      "multiple": false,
      "maxFileBytes": 268435456,
      "presentation": "metrics",
      "deferImagePreview": true,
      "note": "Inspect, add or remove a leading encoding marker. Adding validates the selected encoding; this does not transcode the payload. Maximum 256 MiB.",
      "experience": {
        "automatic": false,
        "single": false,
        "inputMaxLength": 1000000,
        "inputMode": "text",
        "label": "Your text",
        "placeholder": "Type or paste your input…",
        "help": "Up to 1,000,000 characters. Review the settings before running.",
        "action": null
      },
      "mode": "explicit",
      "interactive": false
    },
    "execution": "Browser interface",
    "api": null,
    "browser_agent": {
      "supported": true,
      "name": "run_current_tool",
      "discovery": "WebMCP on the human page in a supporting browser",
      "verification": "See audit/API-AUDIT.md; availability is not verification"
    }
  },
  "markdown": "# Byte order mark editor\n\n- Human page: https://happytails.ai/en/developer-tools/byte-order-mark-editor/\n- Markdown: https://happytails.ai/en/developer-tools/byte-order-mark-editor.md\n- Structured JSON: https://happytails.ai/agents/en/developer-tools/byte-order-mark-editor/index.json\n- Visibility: public\n\n## Tool capabilities\n\n| Property | Value |\n| --- | --- |\n| Tool ID | `byte-order-mark-editor` |\n| Category | developer-tools |\n| Implementation | Registered implementation. Registration alone is not a production-quality guarantee. |\n| Browser execution | Use the visible action or interactive controls. |\n| Browser processing | Browser; see tool notes for network behavior. |\n| HTTP API | Not callable through HTTP. |\n| Browser-agent interface | run_current_tool |\n\n### Implementation notes\n\nInspect, add or remove a leading encoding marker. Adding validates the selected encoding; this does not transcode the payload. Maximum 256 MiB.\n\n### Inputs and settings\n\nNo free-text input is required. Use the file inputs and/or settings below.\n\nAccepted browser files: `See implementation notes`. Choose one file.\n\nBrowser file-input limit: 268435456 bytes in total. HTTP limits can differ.\n\n| Setting | Meaning | Control type | Default | Constraints |\n| --- | --- | --- | --- | --- |\n| `action` | Action | select | \"Inspect\" | Allowed: Inspect, Add marker, Remove marker |\n| `encoding` | Encoding to validate when adding | select | \"UTF-8\" | Allowed: UTF-8, UTF-16LE, UTF-16BE, UTF-32LE, UTF-32BE |\n\n### Browser-agent workflow\n\n1. Open the human page in a browser that supports WebMCP.\n2. Discover the interface exposed by that page; use its actual schema.\n3. Select files on the page first when the tool requires files.\n4. Call `run_current_tool` with valid input and settings.\n5. Inspect the returned result or error and the displayed output. Retrieve files from the displayed download links.\n\nCalls do not automatically copy or download results. Browser permissions still apply. Interface availability alone is not proof of successful execution.\n\n### Planning specification\n\nOne file up to 256 MiB. Adding a marker validates the selected UTF-8, UTF-16 or UTF-32 encoding. Removing a marker strips only a recognized leading marker. No encoding conversion is performed.\n\nThis describes intended requirements. Use the implementation notes, interface schema and observed output to determine current support.\n\n### Complete machine-readable capability record\n\n```json\n{\n  \"id\": \"byte-order-mark-editor\",\n  \"category\": \"developer-tools\",\n  \"built\": true,\n  \"requirements\": \"One file up to 256 MiB. Adding a marker validates the selected UTF-8, UTF-16 or UTF-32 encoding. Removing a marker strips only a recognized leading marker. No encoding conversion is performed.\",\n  \"implementation\": {\n    \"fields\": [\n      {\n        \"key\": \"action\",\n        \"label\": \"Action\",\n        \"value\": \"Inspect\",\n        \"type\": \"select\",\n        \"values\": [\n          \"Inspect\",\n          \"Add marker\",\n          \"Remove marker\"\n        ]\n      },\n      {\n        \"key\": \"encoding\",\n        \"label\": \"Encoding to validate when adding\",\n        \"value\": \"UTF-8\",\n        \"type\": \"select\",\n        \"values\": [\n          \"UTF-8\",\n          \"UTF-16LE\",\n          \"UTF-16BE\",\n          \"UTF-32LE\",\n          \"UTF-32BE\"\n        ]\n      }\n    ],\n    \"files\": true,\n    \"input\": false,\n    \"multiple\": false,\n    \"maxFileBytes\": 268435456,\n    \"presentation\": \"metrics\",\n    \"deferImagePreview\": true,\n    \"note\": \"Inspect, add or remove a leading encoding marker. Adding validates the selected encoding; this does not transcode the payload. Maximum 256 MiB.\",\n    \"experience\": {\n      \"automatic\": false,\n      \"single\": false,\n      \"inputMaxLength\": 1000000,\n      \"inputMode\": \"text\",\n      \"label\": \"Your text\",\n      \"placeholder\": \"Type or paste your input…\",\n      \"help\": \"Up to 1,000,000 characters. Review the settings before running.\",\n      \"action\": null\n    },\n    \"mode\": \"explicit\",\n    \"interactive\": false\n  },\n  \"execution\": \"Browser interface\",\n  \"api\": null,\n  \"browser_agent\": {\n    \"supported\": true,\n    \"name\": \"run_current_tool\",\n    \"discovery\": \"WebMCP on the human page in a supporting browser\",\n    \"verification\": \"See audit/API-AUDIT.md; availability is not verification\"\n  }\n}\n```\n\n## Page guide\n\nInspect, add or remove a UTF byte order mark without changing the encoded payload.\n\nHow can we improve this tool?\n\nReport a problem or share an idea.\n\nPlease leave out private information. Your message and the tool name go to our team via PostHog.\n\n### How to use Byte order mark editor\n\n1. Choose the local file or files.\n2. Review the action and limits, then run the inspection.\n3. Check the result and download a separate output or report.\n\n## Useful next steps\n\n- [Line ending auditor](https://happytails.ai/en/developer-tools/line-ending-auditor/) ([Markdown](https://happytails.ai/en/developer-tools/line-ending-auditor.md))\n\n- [Binary file comparator](https://happytails.ai/en/developer-tools/binary-file-comparator/) ([Markdown](https://happytails.ai/en/developer-tools/binary-file-comparator.md))\n\n- [File hash](https://happytails.ai/en/developer-tools/file-hash/) ([Markdown](https://happytails.ai/en/developer-tools/file-hash.md))\n\n## Inspect the leading bytes\n\nChoose a local file and inspect the detected marker. A missing marker does not identify the file encoding.\n\n### Add or remove explicitly\n\nChoose the action. Adding validates the payload against the selected encoding; conflicting markers and invalid code units are rejected.\n\n### Keep the original\n\nDownload a new binary file. Every byte after the marker is preserved, and the source is never modified.\n"
}