{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"rest-client","slug":"rest-client","name":"REST Client","type":"extension","url":"https://marketplace.visualstudio.com/items?itemName=humao.rest-client","page_url":"https://unfragile.ai/rest-client","categories":["code-editors"],"tags":[],"pricing":{"model":"free","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"rest-client__cap_0","uri":"capability://tool.use.integration.inline.http.request.composition.and.execution","name":"inline http request composition and execution","description":"Enables developers to write HTTP requests directly in `.http` and `.rest` files using a plain-text syntax with `###` delimiters separating multiple requests. Each request is parsed by the extension's lexer, validated against HTTP RFC 2616, and executed within the VS Code process without leaving the editor. The extension renders responses in a split-pane view with syntax highlighting for JSON, XML, and other content types, eliminating the need for external HTTP clients like Postman or curl.","intents":["I want to test API endpoints without switching to Postman or terminal","I need to keep HTTP requests version-controlled alongside my code","I want to document API calls as executable examples in my project"],"best_for":["backend developers building REST APIs","full-stack engineers testing APIs during development","teams wanting API tests co-located with source code"],"limitations":["No built-in request scheduling or automation — each request is manual or triggered by user action","Maximum request/response size limits unknown — large payloads may cause performance degradation","No concurrent request execution — requests execute sequentially","CORS restrictions apply as in browsers — cross-origin requests may fail without proper headers"],"requires":["VS Code (minimum version unknown)","File with `.http` or `.rest` extension","Network connectivity for remote endpoints"],"input_types":["plain text HTTP requests","request headers as key-value pairs","request body as JSON, XML, form data, or raw text"],"output_types":["HTTP response with status code and headers","response body with syntax highlighting","rendered images if response is image MIME type"],"categories":["tool-use-integration","developer-tools"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"rest-client__cap_1","uri":"capability://memory.knowledge.multi.scope.variable.substitution.with.dynamic.generation","name":"multi-scope variable substitution with dynamic generation","description":"Implements a hierarchical variable resolution system supporting environment variables, file-level variables, request-level variables, and prompt variables. The extension provides 8 built-in dynamic variable types ({{$guid}}, {{$timestamp}}, {{$randomInt}}, {{$datetime}}, {{$localDatetime}}, {{$processEnv}}, {{$dotenv}}, {{$aadToken}}) that generate values at request time. Variables are substituted into URLs, headers, and request bodies using mustache-style syntax ({{variableName}}), with auto-completion, hover documentation, and diagnostic validation integrated into the editor.","intents":["I need to use different API keys and base URLs for dev, staging, and production environments","I want to generate unique request IDs or timestamps without manual entry","I need to reference environment variables from my system or .env files in HTTP requests"],"best_for":["developers managing multiple API environments","teams using environment-specific credentials","engineers automating API testing with dynamic values"],"limitations":["Prompt variables require interactive input per request — unsuitable for fully automated testing","Find-all-references only works for file-level variables, not environment or request variables","Go-to-definition navigation unavailable for environment variables","Variable scope resolution order not documented — potential ambiguity if same variable name exists in multiple scopes","No built-in variable encryption — credentials stored in plain text in settings.json or .env files"],"requires":["VS Code settings.json for environment definitions","Optional .env file in workspace for dotenv variables","Azure AD tenant ID or domain for {{$aadToken}} generation"],"input_types":["variable definitions in VS Code settings",".env file with KEY=VALUE pairs","process environment variables","request-level variable declarations"],"output_types":["substituted values in HTTP request URL, headers, and body","generated GUIDs, timestamps, random integers","Azure AD access tokens"],"categories":["memory-knowledge","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"rest-client__cap_10","uri":"capability://memory.knowledge.cookie.management.with.automatic.persistence","name":"cookie management with automatic persistence","description":"Automatically captures and stores cookies from HTTP responses (Set-Cookie headers) and includes them in subsequent requests (Cookie header). The extension maintains a cookie jar per host/domain, respecting cookie attributes like Path, Domain, Expires, and HttpOnly. Developers can view, edit, and clear cookies manually. This enables testing stateful APIs that rely on session cookies without manual cookie extraction and header manipulation.","intents":["I want to test APIs that use session cookies without manually copying cookie values","I need to maintain session state across multiple requests","I want to clear cookies between test runs to simulate fresh sessions"],"best_for":["developers testing session-based APIs","teams validating authentication flows with cookies","engineers testing stateful web services"],"limitations":["Cookie jar storage location and format unknown — unclear if cookies persist across VS Code restarts","Cookie attribute handling (Path, Domain, Expires) may not fully comply with RFC 6265","No cookie encryption — cookies stored in plain text, security risk for sensitive data","No cookie inspection UI — developers must manually view stored cookies","HttpOnly cookie handling unclear — may not prevent JavaScript access in certain contexts"],"requires":["HTTP response with Set-Cookie header","Subsequent requests to same host/domain"],"input_types":["Set-Cookie header from HTTP response"],"output_types":["Cookie header in subsequent requests","stored cookie jar"],"categories":["memory-knowledge","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"rest-client__cap_11","uri":"capability://tool.use.integration.proxy.configuration.and.routing","name":"proxy configuration and routing","description":"Allows developers to configure HTTP and HTTPS proxies for request routing, enabling testing through corporate proxies, VPNs, or traffic inspection tools. Proxy settings are configured in VS Code settings and applied to all requests. The extension supports proxy authentication (Basic Auth) and proxy bypass rules for specific hosts. This enables developers behind corporate firewalls to test external APIs without manual proxy configuration per request.","intents":["I need to route requests through a corporate proxy to access external APIs","I want to inspect API traffic with a proxy tool like Fiddler or Charles","I need to bypass the proxy for internal API endpoints"],"best_for":["developers in corporate environments with proxy requirements","teams using traffic inspection tools for debugging","engineers testing APIs through VPNs or firewalls"],"limitations":["Proxy configuration format and options undocumented — unclear if SOCKS proxies are supported","Proxy authentication mechanism unknown — may only support Basic Auth","Proxy bypass rules format unknown — unclear if regex or wildcard patterns are supported","No proxy health checks or fallback — failed proxy connections may not provide clear error messages","Proxy settings stored in VS Code settings — not easily shareable across team"],"requires":["Proxy server URL and port","Optional proxy authentication credentials","VS Code settings configured with proxy details"],"input_types":["proxy URL","proxy authentication credentials","proxy bypass rules"],"output_types":["HTTP request routed through proxy","HTTP response from proxied endpoint"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"rest-client__cap_12","uri":"capability://code.generation.editing.code.snippet.generation.for.multiple.languages","name":"code snippet generation for multiple languages","description":"Generates executable code snippets in Python, JavaScript, and other languages from composed HTTP requests. The extension analyzes the request (method, URL, headers, body, authentication) and generates equivalent code using popular HTTP libraries (requests for Python, fetch for JavaScript, etc.). Generated snippets include proper error handling, header construction, and authentication setup. This enables developers to quickly convert REST Client requests into production code without manual translation.","intents":["I want to convert my REST Client request into Python code for my application","I need to generate JavaScript fetch code for frontend API calls","I want to quickly prototype API integration code from my tests"],"best_for":["developers translating API tests into production code","teams documenting API usage with code examples","engineers prototyping API integrations"],"limitations":["Supported languages limited to Python, JavaScript, and 'more' — specific list unknown","Generated code completeness unknown — may require manual refinement for production use","Library dependencies not documented — generated code may require external packages","Authentication handling in snippets unknown — may not properly handle all auth methods","Error handling and retry logic not guaranteed — generated code may be minimal","No customization of generated code templates — developers cannot adjust style or patterns"],"requires":["Composed HTTP request in REST Client","Target programming language selection"],"input_types":["HTTP request (method, URL, headers, body, authentication)"],"output_types":["executable code snippet in target language","code with proper imports and error handling"],"categories":["code-generation-editing","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"rest-client__cap_13","uri":"capability://code.generation.editing.syntax.highlighting.and.editor.integration.with.codelens","name":"syntax highlighting and editor integration with codelens","description":"Provides syntax highlighting for HTTP request syntax (methods, headers, URLs, request bodies) and response content (JSON, XML, HTML, plain text). The extension integrates CodeLens actionable links directly in the editor, displaying 'Send Request' links above each request block that developers can click to execute. Syntax highlighting extends to comments, variable references, and request delimiters (###). Auto-completion suggests HTTP methods, headers, MIME types, and variable names as developers type.","intents":["I want syntax highlighting for HTTP requests to catch syntax errors early","I need quick access to send requests without using keyboard shortcuts","I want auto-completion for HTTP headers and methods to speed up request composition"],"best_for":["developers writing HTTP requests frequently","teams using REST Client for API testing","engineers preferring visual feedback while composing requests"],"limitations":["Syntax highlighting limited to built-in content types — custom MIME types may not highlight","CodeLens performance impact unknown — may cause lag in large files with many requests","Auto-completion suggestions may not include custom headers or domain-specific values","No syntax validation or linting — invalid HTTP syntax not flagged until execution","Markdown code block syntax highlighting may conflict with REST Client syntax"],"requires":["VS Code (minimum version unknown)","File with `.http` or `.rest` extension or markdown code block with `http` language tag"],"input_types":["HTTP request syntax in editor"],"output_types":["syntax-highlighted request and response","CodeLens links for request execution","auto-completion suggestions"],"categories":["code-generation-editing","text-generation-language"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"rest-client__cap_14","uri":"capability://code.generation.editing.symbol.navigation.and.variable.reference.tracking","name":"symbol navigation and variable reference tracking","description":"Provides VS Code symbol navigation (Ctrl+Shift+O) to jump to request definitions and file-level variable declarations within `.http` files. Developers can use 'Go to Definition' to navigate to variable definitions and 'Find All References' to locate all usages of file-level variables. This enables quick navigation in large request files with many requests and variables, improving code organization and refactoring.","intents":["I want to quickly jump to a specific request in a large .http file","I need to find all places where a variable is used before renaming it","I want to navigate to variable definitions to understand their values"],"best_for":["developers managing large HTTP request files","teams refactoring request files and variables","engineers maintaining complex API test suites"],"limitations":["Find-all-references only works for file-level variables — environment and request variables not supported","Go-to-definition unavailable for environment variables — only works for request and file variables","Symbol navigation limited to requests and variables — no support for other constructs","No rename refactoring — developers must manually update variable names across file"],"requires":["VS Code (minimum version unknown)","File with `.http` or `.rest` extension containing requests and variables"],"input_types":["request definitions","file-level variable declarations"],"output_types":["symbol list for navigation","definition location for variables","reference list for variables"],"categories":["code-generation-editing","memory-knowledge"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"rest-client__cap_2","uri":"capability://tool.use.integration.multi.method.authentication.with.cloud.identity.integration","name":"multi-method authentication with cloud identity integration","description":"Supports 6 authentication mechanisms: Basic Auth (base64-encoded credentials in Authorization header), Digest Auth (RFC 2617 challenge-response), SSL Client Certificates (file-based), Azure Active Directory (interactive browser-based token flow with cloud environment selection), Microsoft Identity Platform (tenant-aware token generation), and AWS Signature v4 (request signing). Azure AD tokens are generated via {{$aadToken}} variable with parameters for cloud environment (public, cn, de, us, ppe), tenant ID, and audience specification, with token caching behavior unknown.","intents":["I need to test APIs protected by Azure AD or OAuth2 without manually copying tokens","I want to use AWS Signature v4 signing for AWS API calls directly from my editor","I need to test APIs requiring mutual TLS with client certificates"],"best_for":["enterprise developers using Azure AD or Microsoft Identity","AWS-focused teams testing AWS API Gateway or service endpoints","security-conscious teams using mutual TLS authentication"],"limitations":["Azure AD authentication requires interactive browser-based login flow — unsuitable for headless/automated testing","Token caching and refresh mechanism unknown — may require re-authentication per request","AWS Signature v4 credential source and refresh mechanism undocumented","SSL certificate validation strictness and revocation checking behavior unknown","No built-in support for OAuth2 authorization code flow or refresh token handling","Credentials stored in VS Code settings or system keychain — storage mechanism unknown and potentially insecure"],"requires":["Azure AD tenant ID or domain for AAD authentication","AWS credentials in environment variables or system configuration for Signature v4","SSL certificate files (PEM or DER format) for client certificate authentication","VS Code settings configured with authentication parameters"],"input_types":["username and password for Basic Auth","SSL certificate file paths","Azure AD tenant ID and audience","AWS access key and secret key"],"output_types":["Authorization header with credentials","Azure AD bearer token","AWS Signature v4 signed request headers","HTTP 200 or 401 response based on authentication success"],"categories":["tool-use-integration","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"rest-client__cap_3","uri":"capability://text.generation.language.response.preview.with.multiple.rendering.modes","name":"response preview with multiple rendering modes","description":"Renders HTTP responses in a split-pane view with syntax highlighting for JSON, XML, HTML, and plain text. The extension supports multiple preview modes: headers only, body only, full response, and combined request+response view. Image responses are rendered as inline images rather than raw binary. Responses can be folded/unfolded for readability, and the preview font (size, family, weight) is customizable. Raw response bodies can be saved to disk, and response history is auto-saved for later retrieval.","intents":["I want to see formatted JSON responses with syntax highlighting instead of raw text","I need to inspect response headers and body separately","I want to save API responses to files for debugging or documentation"],"best_for":["developers debugging API responses","teams documenting API behavior with response examples","engineers analyzing response headers and status codes"],"limitations":["Maximum response size limits unknown — very large responses may cause rendering lag or memory issues","Image rendering limited to inline preview — no external image viewer integration","Response history stored locally — no cloud sync or sharing across team members","No built-in response comparison or diff tool — manual comparison required for multiple responses","Syntax highlighting limited to common formats (JSON, XML, HTML) — custom content types may render as plain text"],"requires":["VS Code (minimum version unknown)","HTTP response with valid Content-Type header for syntax highlighting"],"input_types":["HTTP response status code","response headers","response body in any format"],"output_types":["formatted response with syntax highlighting","rendered images","saved response files on disk","response history list"],"categories":["text-generation-language","image-visual"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"rest-client__cap_4","uri":"capability://automation.workflow.request.chaining.via.response.variable.extraction","name":"request chaining via response variable extraction","description":"Enables sequential request execution where responses from one request can be captured and used as variables in subsequent requests. The extension maintains request history and allows variables to reference previous response values, enabling workflows like: authenticate (request 1) → extract token from response → use token in API call (request 2). Variable substitution occurs at request time, allowing dynamic request composition based on prior responses. The exact mechanism for response-to-variable extraction (e.g., JSONPath, regex) is undocumented.","intents":["I need to authenticate first, then use the returned token in subsequent API calls","I want to create a resource and use its ID in follow-up requests","I need to test workflows that depend on response values from previous steps"],"best_for":["developers testing multi-step API workflows","teams validating authentication and authorization flows","engineers building integration tests with dependent requests"],"limitations":["Response extraction mechanism undocumented — unclear if JSONPath, regex, or other parsing is supported","No explicit request ordering or dependency declaration — relies on file order and manual sequencing","No conditional branching based on response status or content — all requests execute linearly","Response variable scope and lifetime unknown — unclear if variables persist across file saves or editor sessions","No built-in error handling or retry logic — failed requests may leave subsequent requests in invalid state"],"requires":["Multiple requests in same `.http` or `.rest` file","Variable definitions that reference previous request responses","Successful execution of prior requests to populate response variables"],"input_types":["HTTP response from prior request","variable reference syntax ({{variableName}})"],"output_types":["extracted values from response body","substituted values in subsequent request URL, headers, body"],"categories":["automation-workflow","planning-reasoning"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"rest-client__cap_5","uri":"capability://tool.use.integration.graphql.query.composition.and.execution","name":"graphql query composition and execution","description":"Supports GraphQL query syntax within `.http` and `.rest` files, enabling developers to compose GraphQL queries and mutations with variables. The extension parses GraphQL syntax, provides syntax highlighting, and executes queries against GraphQL endpoints via HTTP POST requests. GraphQL variables are defined in the request body or via the extension's variable system, allowing parameterization of queries without manual string manipulation.","intents":["I want to test GraphQL queries directly from my editor without switching to GraphQL Playground","I need to compose GraphQL mutations with variables for different environments","I want to keep GraphQL queries version-controlled alongside my API tests"],"best_for":["developers building GraphQL APIs","teams using GraphQL for backend queries","engineers testing GraphQL mutations and subscriptions"],"limitations":["GraphQL subscriptions (WebSocket) support unknown — likely limited to query and mutation operations","No built-in schema introspection or autocomplete — developers must manually write queries","GraphQL error handling and validation feedback unknown — errors may not be clearly distinguished from HTTP errors","No support for GraphQL fragments or reusable query components — each query must be self-contained"],"requires":["GraphQL endpoint URL","Valid GraphQL query or mutation syntax","Optional GraphQL variables in request body"],"input_types":["GraphQL query or mutation syntax","GraphQL variables as JSON"],"output_types":["GraphQL response with data and errors fields","HTTP status code and headers"],"categories":["tool-use-integration","text-generation-language"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"rest-client__cap_6","uri":"capability://code.generation.editing.curl.command.parsing.and.code.generation","name":"curl command parsing and code generation","description":"Parses cURL commands and converts them into REST Client request syntax, enabling developers to import existing curl commands from documentation or terminal history. The extension also generates cURL commands from composed requests, allowing export for use in scripts or documentation. This bidirectional conversion supports all cURL options relevant to HTTP requests (headers, authentication, body, method, etc.) and integrates with the extension's variable system.","intents":["I have a cURL command from API documentation and want to test it in VS Code","I want to export my REST Client request as a cURL command for documentation or shell scripts","I need to convert curl commands to REST Client format for team collaboration"],"best_for":["developers migrating from curl-based workflows to REST Client","teams sharing API examples in cURL format","engineers documenting APIs with both cURL and REST Client examples"],"limitations":["cURL option support incomplete — advanced options (e.g., --socks5, --http2) may not be parsed","Generated cURL commands may not preserve exact formatting or option order from original","No support for cURL config files (~/.curlrc) — only inline command parsing","cURL variable syntax (e.g., $variable) may conflict with REST Client variable syntax ({{variable}})"],"requires":["Valid cURL command syntax","cURL command in request file or clipboard"],"input_types":["cURL command string","REST Client request syntax"],"output_types":["REST Client request syntax","cURL command string"],"categories":["code-generation-editing","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"rest-client__cap_7","uri":"capability://tool.use.integration.soap.request.envelope.composition.and.execution","name":"soap request envelope composition and execution","description":"Supports SOAP request composition with XML envelope building snippets and syntax highlighting. Developers can compose SOAP requests with headers, body elements, and namespaces directly in `.http` files. The extension handles SOAP-specific headers (SOAPAction, Content-Type: application/soap+xml) and provides templates for common SOAP patterns. Responses are parsed and rendered with XML syntax highlighting.","intents":["I need to test SOAP web services from my editor","I want to compose SOAP requests with proper envelope structure and namespaces","I need to keep SOAP API tests alongside REST API tests in version control"],"best_for":["developers maintaining legacy SOAP services","teams integrating with SOAP-based third-party APIs","engineers testing SOAP endpoints during development"],"limitations":["WSDL parsing and schema validation unknown — developers must manually construct envelopes","No built-in SOAP fault handling or parsing — errors rendered as raw XML","SOAP attachments (MTOM, SwA) support unknown — likely limited to text-based payloads","No support for SOAP 1.2 specific features — may be SOAP 1.1 only"],"requires":["SOAP endpoint URL","Valid SOAP envelope XML syntax","SOAPAction header value"],"input_types":["SOAP envelope XML","SOAP headers and body elements"],"output_types":["SOAP response envelope","XML-formatted response body"],"categories":["tool-use-integration","text-generation-language"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"rest-client__cap_8","uri":"capability://automation.workflow.environment.scoped.configuration.with.switching","name":"environment-scoped configuration with switching","description":"Implements environment management where developers define multiple named environments (dev, staging, production) in VS Code settings with environment-specific variables. The extension allows switching between environments, and all variable substitutions use the currently active environment's values. Environments can share common variables via a 'shared' environment, and environment-specific variables override shared variables. This enables testing the same request against different backends without modifying the request file.","intents":["I want to test the same API request against dev, staging, and production without changing the request file","I need different API keys and base URLs for each environment","I want to ensure my requests work across all environments before deployment"],"best_for":["teams managing multiple deployment environments","developers testing across dev/staging/production","engineers ensuring environment parity in API behavior"],"limitations":["Environment switching requires manual selection — no automatic switching based on file location or branch","No environment-specific request filtering — all requests execute in current environment","Environment definitions stored in VS Code settings — not easily shareable across team without settings sync","No environment validation or health checks — invalid environment variables cause request failures without clear diagnostics","No environment history or audit trail — unclear which environment was used for past requests"],"requires":["VS Code settings.json with environment definitions","Named environments with variable key-value pairs","Optional 'shared' environment for common variables"],"input_types":["environment name","environment variables as key-value pairs"],"output_types":["substituted request with environment-specific values","HTTP response from environment-specific endpoint"],"categories":["automation-workflow","memory-knowledge"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"rest-client__cap_9","uri":"capability://memory.knowledge.request.history.with.persistence.and.retrieval","name":"request history with persistence and retrieval","description":"Automatically saves all executed requests and responses to a local history store, allowing developers to view, search, and re-execute past requests. History is persisted across VS Code sessions and can be cleared manually. The extension displays request history in a sidebar or command palette, enabling quick access to frequently used requests without re-typing. History entries include request method, URL, timestamp, and response status code.","intents":["I want to quickly re-execute a request I tested earlier without finding the file","I need to see what requests I've made and their responses for debugging","I want to clear sensitive requests from history after testing"],"best_for":["developers iterating on API calls","teams debugging API issues with request history","engineers exploring APIs and needing quick access to past requests"],"limitations":["History stored locally — not synced across devices or team members","No history search or filtering by URL, method, or date — manual browsing required","History entries may include sensitive data (API keys, tokens) — security risk if history is exposed","No history export or sharing — cannot easily document past API interactions","History size limits unknown — may accumulate indefinitely and impact performance"],"requires":["VS Code with REST Client extension installed","At least one executed request to populate history"],"input_types":["executed HTTP request"],"output_types":["history entry with request details and response status","re-executable request from history"],"categories":["memory-knowledge","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"rest-client__headline","uri":"capability://tool.use.integration.http.request.management.extension.for.visual.studio.code","name":"http request management extension for visual studio code","description":"The REST Client extension allows developers to send HTTP requests and view responses directly within Visual Studio Code, streamlining API development and testing workflows without needing external tools.","intents":["best HTTP client for VS Code","HTTP request tool for API testing","send HTTP requests in Visual Studio Code","API development extension for VS Code","manage HTTP requests directly in code editor"],"best_for":["developers working with APIs","users who prefer integrated tools"],"limitations":[],"requires":["Visual Studio Code"],"input_types":["HTTP requests in text files"],"output_types":["HTTP responses"],"categories":["tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":59,"verified":false,"data_access_risk":"high","permissions":["VS Code (minimum version unknown)","File with `.http` or `.rest` extension","Network connectivity for remote endpoints","VS Code settings.json for environment definitions","Optional .env file in workspace for dotenv variables","Azure AD tenant ID or domain for {{$aadToken}} generation","HTTP response with Set-Cookie header","Subsequent requests to same host/domain","Proxy server URL and port","Optional proxy authentication credentials"],"failure_modes":["No built-in request scheduling or automation — each request is manual or triggered by user action","Maximum request/response size limits unknown — large payloads may cause performance degradation","No concurrent request execution — requests execute sequentially","CORS restrictions apply as in browsers — cross-origin requests may fail without proper headers","Prompt variables require interactive input per request — unsuitable for fully automated testing","Find-all-references only works for file-level variables, not environment or request variables","Go-to-definition navigation unavailable for environment variables","Variable scope resolution order not documented — potential ambiguity if same variable name exists in multiple scopes","No built-in variable encryption — credentials stored in plain text in settings.json or .env files","Cookie jar storage location and format unknown — unclear if cookies persist across VS Code restarts","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.7,"quality":0.9,"ecosystem":0.3,"match_graph":0.25,"freshness":0.75,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:25.061Z","last_scraped_at":null,"last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=rest-client","compare_url":"https://unfragile.ai/compare?artifact=rest-client"}},"signature":"H8wnnMrz2CE812x7NLL/11gPJGDGUuQL4bmgsW0KAtMKeH1VU2aCxQY4ijWDjzIXdsMhBHC/RfylnnEg5catDw==","signedAt":"2026-06-21T20:53:00.553Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/rest-client","artifact":"https://unfragile.ai/rest-client","verify":"https://unfragile.ai/api/v1/verify?slug=rest-client","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}