File Utilities and Editing

Available ActionsEach successful request consumes credits as outlined below.

file-mime-type-detect^5crfile-extension-from-mime^5crfile-size-format^5crfile-path-parse^5crfile-path-join^5crfile-path-normalize^5crfile-csv-to-table^5crfile-json-pretty-print^5crfile-json-minify^5crfile-base64-encode^5crfile-base64-decode^5crfile-hash-generate^5cr

Details

A utility for file metadata operations, path manipulation, and content formatting commonly needed when working with files in automation workflows and application development. MIME type detection identifies the content type of files based on filename extensions, covering documents, images, audio, video, archives, and programming languages, while reverse lookup finds appropriate file extensions for a given MIME type. File size formatting converts byte counts into human-readable strings with automatic unit scaling from bytes through petabytes. Path manipulation functions parse file paths into components including directory, filename, name, and extension, join multiple path segments with proper separators, and normalize paths by resolving relative references and redundant separators. CSV to table conversion parses comma-separated data and formats it as an ASCII table with aligned columns for display purposes, also returning structured header and row data. JSON formatting includes pretty printing with configurable indentation for readability and minification that removes all unnecessary whitespace with size reduction statistics. Base64 encoding and decoding handles text-to-base64 conversion for data embedding and transmission. Cryptographic hash generation supports MD5, SHA-1, SHA-256, and SHA-512 algorithms for content integrity verification and fingerprinting.

Use Cases

MIME type detection, file type identification, content type lookup, extension to MIME, MIME to extension, file extension lookup, file size formatting, byte size conversion, human readable file size, KB MB GB formatting, storage size display, file path parsing, path component extraction, directory extraction, filename extraction, extension extraction, path joining, path concatenation, cross-platform path, path normalization, relative path resolution, absolute path conversion, path cleanup, CSV formatting, CSV to table, tabular data display, ASCII table generation, CSV visualization, JSON pretty print, JSON formatting, JSON indentation, readable JSON, JSON beautify, JSON minify, JSON compression, JSON whitespace removal, minified JSON, JSON size reduction, base64 encode, text to base64, base64 encoding, base64 decode, base64 to text, base64 decoding, MD5 hash, SHA1 hash, SHA256 hash, SHA512 hash, content hash, file fingerprint, integrity check, checksum generation, hash generation, file metadata, file utilities, automation file operations, AI agent file handling, LLM file processing, workflow file tools

Connect Your Agent In 5 Min

Watch the setup guide for your platform

Or Install Locally

STDIO connector for Claude Code, Codex, Cursor, Zed, and other LLMs that require STDIO or custom connections. This lightweight connector routes requests to https://api.agentpmt.com/mcp. All tool execution happens in the cloud and the server cannot edit any files on your computer.

npm install -g @agentpmt/mcp-routeragentpmt-setup

curl -X POST "https://api.agentpmt.com/products/purchase" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer ********" \
  -d '{
    "product_id": "694ed536cca5b5123ad00c33",
    "parameters": {
      "action": "file-mime-type-detect",
      "input": "example_input"
    }
  }'

import requests
import json

url = "https://api.agentpmt.com/products/purchase"

headers = {
    "Content-Type": "application/json",
    "Authorization": "Bearer ********"
}

data = {
    "product_id": "694ed536cca5b5123ad00c33",
    "parameters": {
        "action": "file-mime-type-detect",
        "input": "example_input"
    }
}

response = requests.post(url, headers=headers, json=data)
print(response.status_code)
print(response.json())

const url = "https://api.agentpmt.com/products/purchase";

const headers = {
  "Content-Type": "application/json",
  "Authorization": "Bearer ********"
};

const data = {
  product_id: "694ed536cca5b5123ad00c33",
  parameters: {
    "action": "file-mime-type-detect",
    "input": "example_input"
  }
};

fetch(url, {
  method: "POST",
  headers,
  body: JSON.stringify(data)
})
  .then(response => response.json())
  .then(data => console.log(data))
  .catch(error => console.error("Error:", error));

const axios = require('axios');

const url = "https://api.agentpmt.com/products/purchase";

const headers = {
  "Content-Type": "application/json",
  "Authorization": "Bearer ********"
};

const data = {
  product_id: "694ed536cca5b5123ad00c33",
  parameters: {
    "action": "file-mime-type-detect",
    "input": "example_input"
  }
};

axios.post(url, data, { headers })
  .then(response => {
    console.log(response.status);
    console.log(response.data);
  })
  .catch(error => {
    console.error("Error:", error.message);
  });

Login to view your API and budget keys. The example above uses placeholder values. Sign in to see personalized code with your bearer token.

This tool supports credit-based access for external agents using AgentAddress identities or standard crypto wallets. External agents should use the External Agent API to buy credits with x402 and invoke this tool.

1. Buy Credits

Purchase credits via x402 payment (500 credit minimum, 100 credits = $1).

# Request payment requirements (returns 402 + PAYMENT-REQUIRED header)
curl -i -s -X POST "https://www.agentpmt.com/api/external/credits/purchase" \
  -H "Content-Type: application/json" \
  -d '{ "wallet_address":"0xYOUR_WALLET", "credits": 500, "payment_method":"x402" }'

# Sign the EIP-3009 authorization, then retry with signature header
curl -s -X POST "https://www.agentpmt.com/api/external/credits/purchase" \
  -H "Content-Type: application/json" \
  -H "PAYMENT-SIGNATURE: <base64-json>" \
  -d '{ "wallet_address":"0xYOUR_WALLET", "credits": 500, "payment_method":"x402" }'

2. Create a Session Nonce (nonce used in signed balance/invoke)

curl -s -X POST "https://www.agentpmt.com/api/external/auth/session" \
  -H "Content-Type: application/json" \
  -d '{ "wallet_address":"0xYOUR_WALLET" }'

3. Invoke This Tool

Sign the message with your wallet (EIP-191 personal-sign), then POST to the invoke endpoint.

# Sign this message (wallet MUST be lowercased):
# agentpmt-external
# wallet:0xyourwallet...
# session:<session_nonce>
# request:<request_id>
# action:invoke
# product:694ed536cca5b5123ad00c33
# payload:<sha256(canonical_json(parameters))>

curl -s -X POST "https://www.agentpmt.com/api/external/tools/694ed536cca5b5123ad00c33/invoke" \
  -H "Content-Type: application/json" \
  -d '{
    "wallet_address": "0xYOUR_WALLET",
    "session_nonce": "<session_nonce>",
    "request_id": "invoke-uuid",
    "signature": "0x<signature>",
    "parameters": {
      "action": "your_action",
      "your_param": "value"
    }
  }'

Actions(12)

file-mime-type-detect^5cr1 param(1 required)

Detect the MIME type of a file based on its filename/extension. Supports documents, images, audio, video, archives, and programming languages.

inputrequiredstring

The filename to analyze (e.g., 'report.pdf', 'photo.jpg')

file-extension-from-mime^5cr1 param(1 required)

Look up the standard file extension for a given MIME type.

inputrequiredstring

A MIME type string (e.g., 'image/png', 'application/pdf')

file-size-format^5cr1 param(1 required)

Convert a raw byte count into a human-readable size string (KB, MB, GB, etc.).

inputrequiredstring

File size in bytes as a string (e.g., '5242880')

file-path-parse^5cr1 param(1 required)

Break a file path into its component parts: directory, filename, name, and extension.

inputrequiredstring

A file path to parse (e.g., '/home/user/documents/report.pdf')

file-path-join^5cr3 params(1 required)

Join multiple path components into a single path. Provide components as a comma-separated string in input, or use input, input2, and input3 fields for up to three components. At least 2 components required.

inputrequiredstring

First path component, or a comma-separated list of all components

input2string

Second path component (when not using comma separation)

input3string

Third path component (when not using comma separation)

file-path-normalize^5cr1 param(1 required)

Clean up a file path by resolving '..', '.', and redundant separators.

inputrequiredstring

A file path to normalize (e.g., '/home/user/../user/./documents//file.txt')

file-csv-to-table^5cr1 param(1 required)

Parse CSV content and render it as a formatted ASCII table. The first row is treated as headers.

inputrequiredstring

CSV content as a string (e.g., 'Name,Age,City\nAlice,30,New York')

file-json-pretty-print^5cr2 params(1 required)

Format a compact JSON string with indentation for readability.

inputrequiredstring

A valid JSON string to format

indentinteger

Number of spaces per indentation level (0-8)

Default: 2

Range: 0 - 8

file-json-minify^5cr1 param(1 required)

Remove all unnecessary whitespace from a JSON string to produce the most compact representation.

inputrequiredstring

A valid JSON string to minify

file-base64-encode^5cr1 param(1 required)

Encode a text string to base64 using UTF-8 encoding.

inputrequiredstring

The text to encode to base64

file-base64-decode^5cr1 param(1 required)

Decode a base64 string back to UTF-8 text.

inputrequiredstring

A valid base64-encoded string to decode

file-hash-generate^5cr2 params(1 required)

Generate a cryptographic hash of the provided text content.

inputrequiredstring

The content to hash

hash_algorithmstring

Hash algorithm to use: md5, sha1, sha256, or sha512

Values:

md5sha1sha256sha512

Default: sha256

Usage Instructions

Usage guidance provided directly by the developer for this product.

File Utilities and Editing

Name: File Utilities and Editing
Brand: Apoth3osis
SKU: 694ed536cca5b5123ad00c33
Price: 0.05 USD
Availability: InStock

Overview

A collection of file utility operations for working with MIME types, file paths, content formatting (CSV/JSON), base64 encoding/decoding, and cryptographic hashing. Use this tool when you need to manipulate file metadata, transform data formats, or generate hashes without touching the filesystem.

Actions

`file-mime-type-detect`

Detects the MIME type of a file based on its filename/extension. Supports documents, images, audio, video, archives, and programming languages.

Required fields:

input (string) — The filename to analyze (e.g., report.pdf, photo.jpg)

Example:

{
  "action": "file-mime-type-detect",
  "input": "quarterly-report.xlsx"
}

Returns the MIME type (application/vnd.openxmlformats-officedocument.spreadsheetml.sheet), file extension, and category (application).

`file-extension-from-mime`

Looks up the standard file extension for a given MIME type.

Required fields:

input (string) — A MIME type string (e.g., image/png, application/pdf)

Example:

{
  "action": "file-extension-from-mime",
  "input": "audio/mpeg"
}

Returns the matching extension (.mp3) and whether a match was found.

`file-size-format`

Converts a raw byte count into a human-readable size string (KB, MB, GB, etc.).

Required fields:

input (string) — File size in bytes as a string (e.g., "5242880")

Example:

{
  "action": "file-size-format",
  "input": "5242880"
}

Returns "5.00 MB" along with the numeric value and unit.

`file-path-parse`

Breaks a file path into its component parts: directory, filename, name, and extension.

Required fields:

input (string) — A file path to parse (e.g., /home/user/documents/report.pdf)

Example:

{
  "action": "file-path-parse",
  "input": "/home/user/documents/report.pdf"
}

Returns the directory (/home/user/documents), filename (report.pdf), name (report), extension (.pdf), and whether the path is absolute.

`file-path-join`

Joins multiple path components into a single path. You can provide components as a comma-separated string in input, or use the input, input2, and input3 fields for up to three components.

Required fields:

input (string) — First path component, or a comma-separated list of all components

Optional fields:

input2 (string) — Second path component (when not using comma separation)
input3 (string) — Third path component (when not using comma separation)

At least 2 path components are required.

Example (comma-separated):

{
  "action": "file-path-join",
  "input": "/home/user, documents, report.pdf"
}

Example (separate fields):

{
  "action": "file-path-join",
  "input": "/home/user",
  "input2": "documents",
  "input3": "report.pdf"
}

Returns the joined and normalized path (/home/user/documents/report.pdf).

`file-path-normalize`

Cleans up a messy file path by resolving .., ., and redundant separators.

Required fields:

input (string) — A file path to normalize (e.g., /home/user/../user/./documents//file.txt)

Example:

{
  "action": "file-path-normalize",
  "input": "/home/user/../user/./documents//file.txt"
}

Returns the cleaned path (/home/user/documents/file.txt).

`file-csv-to-table`

Parses CSV content and renders it as a formatted ASCII table. The first row is treated as headers.

Required fields:

input (string) — CSV content as a string

Example:

{
  "action": "file-csv-to-table",
  "input": "Name,Age,City\nAlice,30,New York\nBob,25,London\nCarol,35,Tokyo"
}

Returns the row count, column count, headers list, a formatted ASCII table, and the parsed data as structured arrays.

`file-json-pretty-print`

Formats a compact JSON string with indentation for readability.

Required fields:

input (string) — A valid JSON string

Optional fields:

indent (integer, default: 2) — Number of spaces per indentation level (0-8)

Example:

{
  "action": "file-json-pretty-print",
  "input": "{\"name\":\"Alice\",\"age\":30,\"address\":{\"city\":\"New York\",\"zip\":\"10001\"}}",
  "indent": 4
}

Returns the formatted JSON string along with original and formatted lengths.

`file-json-minify`

Removes all unnecessary whitespace from a JSON string to produce the most compact representation.

Required fields:

input (string) — A valid JSON string (can include whitespace/indentation)

Example:

{
  "action": "file-json-minify",
  "input": "{\n  \"name\": \"Alice\",\n  \"age\": 30\n}"
}

Returns the minified JSON, original and minified lengths, and the percentage reduction in size.

`file-base64-encode`

Encodes a text string to base64 using UTF-8 encoding.

Required fields:

input (string) — The text to encode

Example:

{
  "action": "file-base64-encode",
  "input": "Hello, World! This is a secret message."
}

Returns the base64-encoded string along with original and encoded lengths.

`file-base64-decode`

Decodes a base64 string back to UTF-8 text.

Required fields:

input (string) — A valid base64-encoded string

Example:

{
  "action": "file-base64-decode",
  "input": "SGVsbG8sIFdvcmxkISBUaGlzIGlzIGEgc2VjcmV0IG1lc3NhZ2Uu"
}

Returns the decoded text along with encoded and decoded lengths.

`file-hash-generate`

Generates a cryptographic hash of the provided text content.

Required fields:

input (string) — The content to hash

Optional fields:

hash_algorithm (string, default: "sha256") — Algorithm to use: md5, sha1, sha256, or sha512

Example:

{
  "action": "file-hash-generate",
  "input": "This is the content of my document that I want to verify.",
  "hash_algorithm": "sha256"
}

Returns the hex-encoded hash digest, the algorithm used, content length, and hash length.

Common Workflows

Workflow 1: Validate and format incoming data

Use file-mime-type-detect with a received filename to confirm the file type
Use file-size-format to display the file size in a readable format
If the content is JSON, use file-json-pretty-print to format it for review

Workflow 2: Content integrity verification

Use file-base64-decode to decode a received base64 payload
Use file-hash-generate to compute a SHA-256 hash of the decoded content
Compare the hash against an expected value to verify integrity

Workflow 3: Build and normalize file paths

Use file-path-join to combine directory and filename components
Use file-path-normalize to clean up the resulting path
Use file-path-parse to extract individual components for further processing

Important Notes

All operations are stateless text transformations. This tool does not read from or write to the filesystem.
The input field must always be provided as a string, even for numeric values like file sizes.
CSV parsing treats the first row as column headers.
JSON operations (pretty-print and minify) will return an error if the input is not valid JSON.
Base64 encoding/decoding uses UTF-8. Binary data that is not valid UTF-8 cannot be decoded with file-base64-decode.
Unknown file extensions default to the MIME type application/octet-stream.
The indent parameter only applies to file-json-pretty-print and must be between 0 and 8.

About The Developer

Apoth3osis

★15 stars

Joined Agent Payment: August 14, 2025

We build tools that enable AI agents to excel in the mathematical realm.

Our small team develops experimental and unique solutions in the AI arena, with a strong focus on modular computing for agentic applications and custom model deployment. We have handled projects for a variety of applications across many sectors, from algorithmic trading and financial analysis, to molecular simulations and predictions, to habitat and biodiversity monitoring and wildlife conservation.

File Utilities and Editing

Description