agentsclimarketplace

Http api endpoint design

Skill HolobiomicsLab/asb-skill-collections/collections/metabolomics/v2/skills/http-api-endpoint-design

Curated, evidence-grounded skill and software-tool collections for scientific AI agents, generated by the AgenticScienceBuilder

Install
npx -y skills add HolobiomicsLab/asb-skill-collections --skill http-api-endpoint-design

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 14 stars14 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when when you need to expose a multi-step spectral processing workflow (parse → extract → render → annotate → compress) as a web service endpoint that accepts jcamp/RAW/mzML spectral files and must return coordinated output artifacts (modified JCAMP files, peak tables, and PNG images) in a.

The file declares its own license as CC-BY-4.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

6.8 KB, as published. Nobody here has run it

HTTP API Endpoint Design

Summary

Design and implement RESTful HTTP POST endpoints that accept file uploads with spectral data, validate input formats, process the data through a computational pipeline, and return compressed artifact collections. This skill bridges client requests for spectral analysis with backend processing services.

When to use

When you need to expose a multi-step spectral processing workflow (parse → extract → render → annotate → compress) as a web service endpoint that accepts jcamp/RAW/mzML spectral files and must return coordinated output artifacts (modified JCAMP files, peak tables, and PNG images) in a single response.

When NOT to use

  • Input spectral data is already in a processed binary format incompatible with the chem-spectra-app parser
  • Client application requires streaming or real-time response rather than a single atomic payload
  • Output artifacts exceed practical ZIP archive size limits for your deployment environment

Inputs

  • POST request body with spectral file attachment (.dx or .jdx JCAMP format)
  • Spectral data in jcamp, RAW, or mzML format

Outputs

  • ZIP archive containing modified JCAMP file(s) with peak annotations
  • PNG image renderings of spectral data with annotated peaks
  • Peak table artifacts

How to apply

Define a POST endpoint (e.g., /zip_jcamp_n_img) that receives a spectral file attachment (.dx or .jdx format). Parse and validate the input using a dedicated file parser (chem-spectra-app). Extract spectral peaks and generate peak tables from the parsed data. Render the spectral data as PNG images with annotated peaks. Incorporate peak table annotations into modified JCAMP output file(s). Compress all output artifacts (JCAMP and PNG files) into a single ZIP archive. Return the ZIP with appropriate MIME type and HTTP headers. This design ensures the client receives all derived data products in one atomic transaction, reducing round-trip overhead.

Related tools

Examples

curl -X POST -F '[email protected]' http://localhost:3007/zip_jcamp_n_img -o output.zip

Evaluation signals

  • HTTP POST request to the endpoint returns status 200 with a valid ZIP archive in the response body
  • ZIP archive contains expected files: at least one modified JCAMP file and one PNG image per input spectrum
  • Response MIME type is 'application/zip' and Content-Disposition header specifies appropriate filename
  • Peak table data extracted from JCAMP is non-empty and matches the annotations rendered in PNG images
  • Input validation rejects malformed or unsupported file formats (not jcamp/RAW/mzML) with a descriptive HTTP 400 error

Limitations

  • Endpoint design assumes single spectral file input per request; handling multiple files in one request requires additional multiplexing logic
  • RAW and mzML file processing depends on proteowizard/pwiz-skyline Docker service availability and correct environment configuration
  • No explicit timeout or file size limits mentioned; large spectral files may cause memory exhaustion or slow response times
  • Peak annotation accuracy and PNG rendering quality are dependent on upstream chem-spectra-app parser correctness and configuration

Evidence

  • [other] Receive POST request with spectral file attachment in .dx or .jdx format at the /zip_jcamp_n_img endpoint: "Receive POST request with spectral file attachment in .dx or .jdx format at the /zip_jcamp_n_img endpoint."
  • [other] Parse and validate the input spectral file format using the chem-spectra-app file parser: "Parse and validate the input spectral file format using the chem-spectra-app file parser."
  • [other] Extract spectral peaks and generate peak tables from the parsed data: "Extract spectral peaks and generate peak tables from the parsed data."
  • [other] Generate PNG image renderings of the spectral data with annotated peaks: "Generate PNG image renderings of the spectral data with annotated peaks."
  • [other] Compress all output artifacts (JCAMP files and PNG images) into a single ZIP file: "Compress all output artifacts (JCAMP files and PNG images) into a single ZIP file."
  • [readme] This backend web service provides NMR/IR/MS processing for jcamp/RAW/mzML files: "This backend web service provides NMR/IR/MS processing for jcamp/RAW/mzML files."
  • [other] Return the ZIP archive to the client with appropriate MIME type and headers: "Return the ZIP archive to the client with appropriate MIME type and headers."

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.