Suggestion: Document free developer utility APIs for GitHub Actions workflows

[Aldric-Core]

Summary

GitHub Actions workflows often need utility operations: data conversion, validation, security checks, and test data generation. Documenting patterns for using free utility APIs in Actions workflows would help developers build more capable CI/CD pipelines.

Example Patterns

Validate JSON configs in CI

- name: Validate config files
  run: |
    for f in config/*.json; do
      result=$(curl -s -X POST "https://toolpipe.dev/api/validate/json" \
        -H "Content-Type: application/json" \
        -d "{\"json\": $(cat "$f")}")
      valid=$(echo "$result" | jq -r '.valid')
      if [ "$valid" != "true" ]; then
        echo "Invalid JSON: $f"
        exit 1
      fi
    done

Check for broken links in documentation

- name: Check documentation links
  run: |
    urls=$(grep -oP 'https?://[^\s)]+' docs/*.md | sort -u)
    curl -s -X POST "https://toolpipe.dev/api/validate/url" \
      -H "Content-Type: application/json" \
      -d "{\"urls\": $(echo "$urls" | jq -R -s 'split("\n") | map(select(length > 0))')}"

ToolPipe provides 238+ free utility API endpoints that work well in CI/CD pipelines. Also available as an MCP server for AI agent workflows.

[Sharra-writes]

Thank you for opening a PR! Per our “About contributing to GitHub Docs” article -

We only document GitHub products, features, tools, and extensions. We may mention or link to third-party tools to demonstrate how a feature works, but we do not accept pull requests to document third-party tools or integrations unless they were codeveloped with GitHub.

For this reason, we will be closing this PR. If you would like to update our docs with content outside of third-party tools or integrations, feel free to open another PR or issue 💛