Registered Agent (standalone)

A registered agent receives service of process and official notices on behalf of an entity. SwyftFilings offers Registered Agent as a standalone service so partners can order RA for an existing entity without a full formation package.

Related: Service Filings overview · State requirements reference

When to use this flow

Use the standalone Registered Agent service (not the incorporation package) when you are only seeking to appoint a Registered Agent in a given state. If the customer is also forming a new entity, use the incorporation flow and add filings as guided by your SwyftFilings representative. See Incorporation Service Example for package flows.

Service slug and catalog

1. Call Get Services and select the standalone Registered Agent entry (standalone: true).
2. Use that slug for Get Service Configuration and Create New Order.

Examples use registered-agent. Replace with the slug from your environment.

API flow

Step	Method	Endpoint
1. List services	GET	/service-carts
2. Configuration and catalog	GET	/service-carts/{service}
3. NAICS (if required)	GET	/business-classifications
4. Create order	POST	/orders
5. Get order (optional)	GET	/orders/{order_uuid}
6. Get timely Order status changes and Requests for Information on your Webhook

Example: List services

GET {baseUrl}/service-carts
Authorization: Bearer {token}

{
  "success": true,
  "data": [
    {
      "slug": "registered-agent",
      "name": "Registered Agent",
      "description": "Designate a registered agent in a specific state.",
      "allows_addons": false,
      "standalone": true,
      "nested_services": []
    }
  ]
}

State-specific requirements (discovery)

API-driven configuration: For each target state, call Get Service Configuration with your Registered Agent service slug for each state where the entity needs an agent. Build the order using the returned input_fields and catalog.

• input_fields return the baseline required and optional keys, types, and validation_rules for that state and product. Additional inputs may be required during processing based on jurisdiction-specific or filing-specific conditions.
• catalog lists line items with sku, name, price, optional fees by state, and conditions (for example incompatible SKUs).

Example: Get Service Configuration

Request (replace {baseUrl}, {token}, and the slug):

GET {baseUrl}/service-carts/registered-agent?state=TX&business_type=LLC
Authorization: Bearer {token}

Abbreviated success payload:

{
  "success": true,
  "data": {
    "name": "Registered Agent",
    "slug": "registered-agent",
    "description": "Designate a registered agent in a specific state.",
    "input_fields": [
      {
          "name": "First Name",
          "key": "first_name",
          "type": "string",
          "description": "First name of the user",
          "questionnaire_copy": "What is your first name?",
          "validation_rules": [
              "string",
              "max:100",
              "regex:/^[\\p{L}]+([\\s\\-'.]*[\\p{L}]+)*\\.?$/u"
          ],
          "default_value": null,
          "options": null,
          "is_sensitive": false,
          "required": true
      },
      {
          "name": "Last Name",
          "key": "last_name",
          "type": "string",
          "description": "Last name of the user",
          "questionnaire_copy": "What is your last name?",
          "validation_rules": [
              "string",
              "max:100",
              "regex:/^[\\p{L}]+([\\s\\-'.]*[\\p{L}]+)*\\.?$/u"
          ],
          "default_value": null,
          "options": null,
          "is_sensitive": false,
          "required": true
      },
      {
          "name": "Email",
          "key": "email",
          "type": "string",
          "description": "Email address",
          "questionnaire_copy": "What is your email address?",
          "validation_rules": [
              "email:rfc,dns",
              "max:255"
          ],
          "default_value": null,
          "options": null,
          "is_sensitive": false,
          "required": true
      },
      {
          "name": "Phone Number",
          "key": "phone_number",
          "type": "string",
          "description": "Phone number",
          "questionnaire_copy": "What is your phone number?",
          "validation_rules": [
              "string",
              "size:10",
              "regex:/^(?![01])\\d+$/"
          ],
          "default_value": null,
          "options": null,
          "is_sensitive": false,
          "required": true
      },
      ...
    ],
    "catalog": [
      {
        "sku": "SF_RA_EXAMPLE_0",
        "name": "Registered Agent Service",
        "item_type": "product",
        "price": 149,
        "package": false
      }
    ]
  }
}

Example: Create order

POST {baseUrl}/orders
Authorization: Bearer {token}
Content-Type: application/json

{
  "service": "registered-agent",
  "email": "[email protected]",
  "first_name": "Jane",
  "last_name": "Doe",
  "phone_number": "5551234567",
  "consent_sms": false,
  "business_data": {
    "name": "Acme Holdings LLC",
    "formation_state": "TX"
  }
}

Jurisdiction

Set business_data.formation_state to the state where registered agent service is required.

Use the keys returned by Get Service Configuration to determine how jurisdiction fields should be populated.

Fulfillment

1. Order processing: After creation or submission, SwyftFilings evaluates the order and proceeds with service activation.
2. Follow-up requirements: In some cases, additional inputs may be requested during processing depending on the service configuration.
3. Webhooks: Use order_status_changed to track progress and get Rejections or Information Requests.
4. Completion: The order is complete once registered agent service is successfully established and confirmation is provided.

Errors and edge cases

• 422 Validation: Field keys or values that fail validation_rules return errors keyed by field name.
• Entity type: Catalog conditions.applicable_biz_types may restrict certain SKUs to specific entity types.
• Additional requirements: Some requirements identified during processing may require follow-up submission.